The Decentralized Data Access Revolution
summary
Argues that shifting from a push/ingest to a serve and pull model cuts duplication and time-to-insight by letting domains own and publish consumable analytical Data Mesh products, backed by a domain-agnostic shared data platform, automated catalog and virtualization layer. Recommends federated governance, product-thinking for datasets, and closer operational/analytical integration. Warns decentralization is pointless for very small orgs (~50–100 people) and can create silos if governance, discoverability and reference-data strategies aren’t enforced.
AI-written summary · about
chapters (16)
- 0:00Decentralization in data
- 1:56Centralized vs decentralized
- 3:21Domain-driven design
- 5:52Data mesh model
- 7:16Shared platform & products
- 8:42Federated governance
- 10:11Architecture challenges
- 12:20Domain decomposition
- 13:25Product thinking for data
- 14:28Unifying operational & analytical
- 15:53Data fabric & platform
- 17:04How not to mess up data mesh implementation
- 17:48When to decentralize
- 18:52Data lake purpose
- 19:33Balancing approaches
- 20:15Closing remarks
related talks
39mData Mesh: Why, What and How
36mIntroducing Data Mesh A Paradigm Shift In Analytical Data Management Architecture
47mModern Data Architecture: Breaking the Big Data Monolith
20mEmbracing Data Mesh: A Modern Strategy for Scalable Data Management
48mData Mesh Paradigm Shift in Data Platform Architecture -
43mUntangling Data Mesh: A paradigm shift in Big Data
01h 00mData Mesh: Beyond the Data Lake
52mFrom Data Mess to Data Mesh: Navigating People, Process & Platforms
