Data Mesh
A decentralized approach to analytical data in which business domains own and publish their data as products under shared governance.
Data mesh targets the bottleneck of a single central data team by making the teams closest to the data responsible for its quality, which can speed up analytics in large organizations with many domains.
A B2B company makes its sales operations team own an opportunities data product in the lakehouse, with a documented schema, a 6-hour freshness target and quality tests, which finance and marketing query without filing tickets.
Data mesh needs mature domain teams, platform engineering and governance; in small firms it mostly adds overhead. It is an organizational model, not a product, so buying a tool does not create one.
Zhamak Dehghani described four principles: domain-oriented ownership of analytical data; data as a product that is discoverable, addressable, trustworthy and self-describing; a self-serve data infrastructure platform; and federated computational governance, in which global standards are automated in the platform. Data products can physically live in a Data Lakehouse, while Data Governance policies for access, privacy and interoperability apply across all domains.
AI Governance, Systems Architecture
Martin Fowler (Zhamak Dehghani) — Data Mesh Principles and Logical Architecture — https://martinfowler.com/articles/data-mesh-principles.html; AWS — What is a Data Mesh? — https://aws.amazon.com/what-is/data-mesh/
