Learn vocabulary for defining domain boundaries, assigning data ownership, and discussing data responsibility.
0 / 5 completed
1 / 5
What is a 'data domain' in Data Mesh?
A data domain maps to a business domain (e.g., Orders, Customers, Payments) — the team responsible for that business area also owns and serves its data products.
2 / 5
What is 'source-aligned domain' in Data Mesh?
A source-aligned domain produces data products that represent the data generated by its operational systems — e.g., the Orders domain serving order events and order snapshots.
3 / 5
What is a 'consumer-aligned domain' in Data Mesh?
A consumer-aligned domain creates data products shaped for specific consumption use cases — e.g., an Analytics domain that aggregates data from Orders, Customers, and Products for reporting purposes.
4 / 5
What does 'data steward' mean in domain ownership?
A data steward is a named person responsible for a domain's data products — ensuring quality, managing access, communicating SLAs to consumers, and handling governance compliance.
5 / 5
What is 'Conway's Law' implication in Data Mesh domain design?
Conway's Law states that systems reflect organisational communication structures. In Data Mesh, domain boundaries should align with team boundaries so that data ownership is natural, not imposed across team lines.