Open the editor

Data mesh

Domain teams own and publish their data as products, on a shared self-serve platform.

Data mesh diagram: Domains, Data products, Data catalog, Self-serve data platform, Federated governance

Data mesh, defined by Zhamak Dehghani, is an organisational architecture for analytical data. Instead of one central data team piping everything into one warehouse, each business domain owns its analytical data and publishes it as data products, with an owner, a schema, quality guarantees and documentation. A central platform team provides the self-serve tools those domains build on.

It rests on four principles: domain ownership, data as a product, a self-serve data platform and federated computational governance. Most of the work is organisational; the technology can be a familiar warehouse or lakehouse underneath.

The parts of the pattern

Domains
Orders, payments and marketing teams, each responsible for its own data end to end.
Data products
Published, documented, versioned datasets with an owner and service levels.
Data catalog
Where consumers discover products, their schemas, owners and quality.
Self-serve data platform
Shared storage, pipeline tooling, access control and monitoring, run by a platform team.
Federated governance
Standards agreed across domains (naming, privacy, interoperability), enforced by the platform where possible.

How it works

  1. The orders team builds an "orders" data product from its service data, using the platform's pipeline tools.
  2. It registers the product in the catalog with a schema, owner and freshness guarantee.
  3. Analysts find it in the catalog and query it alongside the payments product.
  4. Governance rules, such as masking personal data, are applied automatically by the platform.

When to use it, and when not to

Good fit

  • A large organisation where a central data team has become the bottleneck.
  • Many domains with their own data expertise and appetite for ownership.
  • You can fund a real platform team.

Think twice

  • A small company with one data team: a well-run central warehouse is simpler.
  • Domains do not have the people or will to own data products.
  • Treating it as a tool purchase: data mesh is mostly an operating model.

Edit this diagram

Click Open the diagram in the editor to get your own copy, saved in your browser. Rename the boxes to match your system, swap the generic boxes for technology icons from the palette, then export a PNG, SVG or PDF, or share a link. No sign-up.