Reporting, Metrics, Analytics, Insights, Optimization Questions etc typically arrive closer, if not after the product launch. Its one of those "we don't know what we need". Hence the focus of the system's architecture is on extendibility of the product, and scalability. Most of the time, data is not the product, unless you're building some data mining, statistics engine etc type of product. Data is simply "the state of the system at rest", there is operational (hot) data and historical (cold) data, both facilitating a business transaction/process. Pre-moulding data into N views needed for Y consumers would mean that 100% of the time you're doing something which might be used 100-X% of the time. This duality of purpose will increase system load on every operation unless this shaping is not externalized in a separated process with its own resources etc etc. Maybe I didn't get it...
Complimentary to any warehouse lake, lake house, or mesh... or whatever new concept of data storage governance and security model is thought up in the future
How do you manage data definitions for when a domain wants to exposure entities/data elements from another domain? Do you ensure name spacing or similar is applied to ensure resolving the references are uniquely identified?
Reporting, Metrics, Analytics, Insights, Optimization Questions etc typically arrive closer, if not after the product launch. Its one of those "we don't know what we need". Hence the focus of the system's architecture is on extendibility of the product, and scalability.
Most of the time, data is not the product, unless you're building some data mining, statistics engine etc type of product. Data is simply "the state of the system at rest", there is operational (hot) data and historical (cold) data, both facilitating a business transaction/process.
Pre-moulding data into N views needed for Y consumers would mean that 100% of the time you're doing something which might be used 100-X% of the time. This duality of purpose will increase system load on every operation unless this shaping is not externalized in a separated process with its own resources etc etc.
Maybe I didn't get it...
Very informative video. Thank you!
Complimentary to any warehouse lake, lake house, or mesh... or whatever new concept of data storage governance and security model is thought up in the future
How do you manage data definitions for when a domain wants to exposure entities/data elements from another domain? Do you ensure name spacing or similar is applied to ensure resolving the references are uniquely identified?