Data Mesh, Next
summary
A roadmap for moving Data Mesh from early adopters to the majority with concrete checkpoints: a domain ownership readiness spider (modern engineering, executive support, long-term commitment), phased rollout (explore, expand, exploit) that starts with a few domains, measurable objectives such as increasing domains that both provide and consume analytical data, and engineering guards like fitness functions to verify direction. Technology gaps call for data sharing APIs that preserve time semantics and interoperable policy as code enforceable at access.
AI-written summary · about
chapters (7)
- 0:00Intro
- 2:40The Chasm
- 8:06The Litmus Test
- 11:17Questions
- 12:13Organization
- 17:27Business Driven
- 23:05Platform Software
related talks
31mData Mesh In Practice – How To Set Up A Data Driven Organization
20mEmbracing Data Mesh: A Modern Strategy for Scalable Data Management
51mData Mesh – Successful with People, Process, and Technology
39mData Mesh: Why, What and How
41mWhat is a Data Mesh - And How Not To Mesh it Up
47mData Mesh - a hot air balloon?
52mFrom Data Mess to Data Mesh: Navigating People, Process & Platforms
25mRewire For Data Mesh: Atomic Steps To Rewire The Sociotechnical Backbone Of Your Organization