From Data Mess to Data Mesh: Navigating People, Process & Platforms
summary
Argues that data mesh is a socio-technical shift not a product: four principles (domain ownership, data as a product, self-service platform, federated governance), often multi-year and immature tooling so teams build custom CLIs and integrations. Recommends cloud‑first landing zones using well‑architected frameworks, treating a lakehouse or data catalog as incremental steps, using event‑storming to define data products, tracking KPIs, and starting small — many clients see value before full decentralization but must accept org changes and substantial engineering work.
AI-written summary · about
chapters (11)
- 0:00Intro
- 1:39Agenda
- 2:28What is a data mesh?
- 10:06Considerations for the journey
- 20:58Key takeaways
- 21:51Tracing a journey from mess to mesh
- 33:52Key takeaways
- 34:39Evolutionary considerations (with top tips)
- 49:16Key takeaways
- 50:02Conclusion
- 51:24Outro
related talks
51mData Mesh – Successful with People, Process, and Technology
23mHow To “Data Mesh”: What You Need To Know To Make It Real
38mData Mesh, Now
20mEmbracing Data Mesh: A Modern Strategy for Scalable Data Management
36mIntroducing Data Mesh A Paradigm Shift In Analytical Data Management Architecture
43mUntangling Data Mesh: A paradigm shift in Big Data
34mBest and Worst Days of Data Mesh
43mWhen design meets data: Using Data Mesh for a consumer and business-driven data strategy