“Domain-oriented decentralized data ownership and architecture. Data as a product. Self-serve data infrastructure as a platform. Federated computational governance.”Zhamak Dehghani · Data Mesh Principles and Logical Architecture · 2020 · Data Mesh Principles and Logical Architecture, martinfowler.com (2020) — cele patru principii, în ordinea din articol
A data product has an owner, a schema, an SLA and an address — otherwise it is just a table.
The problem the data mesh solves is organisational: the central data team becomes a bottleneck and does not know the semantics of twenty domains; when an order "was cancelled" means something different in logistics than in billing, the central team finds out last. The first principle moves ownership to the domain. The second requires what the domain publishes to be a product: a dataset with a schema, an owner, an SLA, documentation, an access address — discoverable, trustworthy, interoperable. The third, the self-serve platform, is what makes the first two possible: teams publish without each building their own infrastructure. The fourth, federated computational governance, says the shared rules — what counts as PII, which formats, which identifiers — are code checked automatically, not a committee. The trap: a mesh without a platform is twelve incompatible warehouses with a new name. And scale matters: for a company with a single data team, a well-modelled central warehouse is the right answer, not a scaled-down mesh.
Why it matters Most "mesh" failures are platform failures: ownership was decentralised before there was anything shared to publish on.