Data Mesh

A data mesh moves responsibility for data closer to the domain that understands its meaning and production. A domain publishes a data product with discoverable interfaces, documented semantics and quality expectations instead of merely sending raw tables to a central team. Shared infrastructure reduces the operational burden, while federated governance establishes rules that let products work together. These principles are interdependent: distributing storage without product ownership or common standards does not create a mesh. The approach concerns operating responsibilities and interfaces as much as technology, and can use warehouses, lakehouses or other platforms underneath.

A practitioner identifies domains and consumer needs, defines ownership and builds publication standards for data products. They establish contracts for schema, meaning, access and reliability, along with a platform that makes those responsibilities feasible for domain teams. Useful artifacts include a product catalog, ownership matrix and shared governance rules. The implementation should test whether consumers can find, understand and use a product without reconstructing the producer's internal systems. Success is measured through dependable consumption and clear responsibility, not the number of decentralized databases created.

Data mesh can increase coordination costs when domains lack engineering capacity or shared standards. Renaming existing tables as products does not improve usability, and decentralized ownership can fragment definitions. The approach is most useful when ownership and cross-domain demand justify its overhead. A review should examine actual consumer experience and incident responsibility; a platform diagram alone cannot establish that a functioning data-product operating model exists.