🕸️ Data Mesh: Decentralising Data Ownership
An interactive 3D network of domain-owned data products where toggling centralized versus mesh architectures changes simulated data-request latency and governance-compliance indicators.
A 3D network of domain-owned data products compares a decentralized data mesh against a centralized warehouse, showing how routing every request through one hub raises latency while a federated governance layer keeps compliance in check either way.
🔬 What It Demonstrates
In mesh mode, requests travel directly between domain nodes and latency stays low as domains are added. In centralized mode, every request is rerouted through a single hub, so latency grows with both domain count and request rate — a visible bottleneck.
🎮 How to Use
Toggle between architectures, adjust domain count and request rate, and raise governance strictness to see the compliance rate change. Green particles pass their governance check; red particles are flagged as violations.
💡 Did You Know?
Zhamak Dehghani's 2019 "data mesh" model rests on four principles: domain ownership, data-as-a-product, self-serve infrastructure, and federated computational governance — decentralising storage without decentralising standards.
Interactive 3D network of domain-owned data products where reassigning ownership shows how a data mesh decentralizes pipelines while a federated layer keeps governance intact.
3D · Three.js / WebGL renderer · 60 FPS target · runs fully client-side, no install