Data mesh architecture
Decentralize ownership, federate governance, and treat data as a product across autonomous domain teams.
Ingredients
- • Domain-oriented data owners
- • Self-serve data platform
- • Federated computational governance
- • Data product contracts (schemas, SLAs)
- • Polyglot persistence layer
Steps
- Identify bounded contexts and assign domain owners.
- Define data product interfaces with versioned schemas.
- Provision self-serve infrastructure per domain.
- Implement federated governance policies (access, PII, lineage).
- Expose data products via discoverable catalog endpoints.
- Monitor SLAs and iterate on consumer feedback loops.
Notes
Zhamak Dehghani's principles apply. Start with one domain, prove the operating model, then scale horizontally. Avoid central bottlenecks — the platform team builds the mesh, not the monolith.