Data Systems
Data Mesh
Data Mesh is a way to think about analytical data ownership. Instead of one central team trying to understand every dataset, domain teams own data products that other teams can trust and use.
Why This Matters
As systems grow, data problems become ownership problems. A central platform can provide tools, standards, and governance, but the meaning of the data usually lives closest to the domain.
Core Idea
- Domains own their data products.
- Data products have clear contracts.
- A self-serve platform makes publishing and consuming data easier.
- Governance is federated, not ignored.
System Architecture
flowchart LR Platform[Self-serve data platform] --> Orders[Orders data product] Platform --> Payments[Payments data product] Platform --> Search[Search data product] Orders --> Analytics[Analytics consumers] Payments --> Analytics Search --> Analytics Governance[Federated governance] -. standards .-> Orders Governance -. standards .-> Payments Governance -. standards .-> Search
What To Watch
- schema contracts
- data quality ownership
- discoverability
- lineage
- access control
- product thinking for datasets
Takeaways
- Data Mesh is less about tools and more about ownership.
- Platform teams still matter, but they enable domains instead of owning every dataset.
- The hard part is balancing autonomy with shared standards.