How To “Data Mesh”: What You Need To Know To Make It Real
summary
Argues the data mesh sits in the middle of a three‑stage maturity path—data ocean, data mesh, data factories—not a single product, and less than a third of organizations get transformational outcomes today. Recommends catalogue/visibility first, then domain teams with centralized coordination, shift‑left security and finance at the domain level. Cites BigQuery, Dataproc, Dataflow and real cases (L’Oreal, Delivery Hero, Carrefour, Fidelity); claims successful adopters run 2–4× faster and build repeatable data products.
AI-written summary · about
chapters (9)
- 0:00Start
- 0:03Bruno Aziza
- 1:21First Exposure to the Data Mesh
- 3:29Three D's of the Data Mesh
- 3:48The Distractors
- 11:13The Allocation of Resources at the Domain Level
- 12:55The Data Ocean
- 18:42Are You Operating at a Scale That Requires Decentralization
- 19:52Do You Treat Your Data Mesh as a Technical Solution or as an Operating Model That Continuously Evolves Around over Time
related talks
51mData Mesh – Successful with People, Process, and Technology
31mData Mesh In Practice – How To Set Up A Data Driven Organization
52mFrom Data Mess to Data Mesh: Navigating People, Process & Platforms
41mWhat is a Data Mesh - And How Not To Mesh it Up
43mWhen design meets data: Using Data Mesh for a consumer and business-driven data strategy
30mHow To Select Technology For Data Mesh
20mEmbracing Data Mesh: A Modern Strategy for Scalable Data Management
43mUntangling Data Mesh: A paradigm shift in Big Data