Data Mesh, Now
summary
Three years after the idea appears, the claim is that Data Mesh succeeds by four concrete shifts: domain ownership, data as a product, self‑serve platform and federated computational governance implemented as policy‑as‑code. About ~200 lead adopters and a learning Slack of 5,000 members validate early interest but reveal high integration costs: adapting warehouses, catalogs, observability and event/table access into multimodal “data product” output ports is hard. The architecture is built conceptually; many teams report partial success, not turnkey solutions.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 3:14Welcome
- 4:14Technology Naming
- 6:22Challenges
- 6:40Distributed Data Mesh
- 9:38Alternative Approach
- 10:29Four Principles
- 16:31Data Mesh Architecture
- 19:39Data Mesh Today
- 22:03Fun Facts
- 22:15Data Fabric vs Data Mesh
- 25:36Misconceptions
- 29:54Drama
- 31:11Community
- 32:13Adopters
- 33:35Integration
- 34:30Complexities
- 36:34Next steps
- 37:14What comes next
related talks
51mData Mesh – Successful with People, Process, and Technology
36mData Mesh and Its Superpowers
39mData Mesh: Why, What and How
47mData Mesh - a hot air balloon?
43mUntangling Data Mesh: A paradigm shift in Big Data
50mData Mesh: the new paradigm for data management
20mEmbracing Data Mesh: A Modern Strategy for Scalable Data Management
31mData Mesh In Practice – How To Set Up A Data Driven Organization