Federated data mesh
Domains own their data as products; a federated query engine joins across them with pushdown; a semantic layer gives everyone one metric vocabulary.
What this design does
The mesh answer to the central-warehouse bottleneck: each domain team publishes a data product it owns and documents, a federated engine plans cross-domain joins that push filters down to each source, and the semantic layer pins down what 'active customer' actually means — once, for everyone.
The patterns it composes
- Data products / data mesh — domains own, document and serve their data — no central team bottleneck
- Federated query engine — one SQL plan spanning heterogeneous sources
- Predicate & projection pushdown — sources ship surviving rows, not tables
- Semantic / metrics layer — shared definitions — one 'revenue', not five
- Lineage & catalog — every product findable, every column traceable
Import it, attach your own numbers, and verify the design against failures — or read the engineering notes.