Best and Worst Days of Data Mesh
summary
Claims that data mesh is a business transformation not just an architecture, with the very first data mesh project originating inside the company and a pharma client turning domain-owned outputs into sellable insights. Requires concrete prerequisites: data product owner roles, data pipelines as code, and cloud continuous delivery practices. Start small — three or four domain-aligned data products first — pair platform teams with operational owners, and expect organizational change, not a purely technical fix.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:08Welcome
- 1:47What is Data Mesh
- 3:43Business and organizational impacts
- 5:17Team structure
- 7:28Data strategy
- 10:04Data mesh vs centralized platforms
- 12:53Bad and good examples
- 15:55Product focus
- 17:36Technology maturity
- 20:49Are you ready
- 27:01Top down vs bottom up
- 30:52Is this for everyone
- 32:50The bottleneck problem
- 33:54Outro
related talks
51mData Mesh – Successful with People, Process, and Technology
43mWhen design meets data: Using Data Mesh for a consumer and business-driven data strategy
52mFrom Data Mess to Data Mesh: Navigating People, Process & Platforms
31mData Mesh In Practice – How To Set Up A Data Driven Organization
43mUntangling Data Mesh: A paradigm shift in Big Data
36mData Mesh and Its Superpowers
41mWhat is a Data Mesh - And How Not To Mesh it Up
25mRewire For Data Mesh: Atomic Steps To Rewire The Sociotechnical Backbone Of Your Organization