Rewire For Data Mesh: Atomic Steps To Rewire The Sociotechnical Backbone Of Your Organization
summary
Data Mesh reframes analytical data as domain-owned data products with computational APIs, not files or tables, and claims decentralization fixes friction and scale. Vendors add features (AWS Lake Formation cross-account sharing, Google Dataplex, Starburst federated queries) while community grows to ~6,600 members; common anti-patterns are single-cloud or single-vendor meshes and “mesh on top of pipelines.” Measurable goals: cut lead time to use data, raise change/deploy frequency, lower change-fail rate and mean time to recovery; costly rewrites (hundreds of millions, ~3 years) show integration remains hard.
AI-written summary · about
chapters (5)
- 0:00Start
- 0:17Rewire for Data Mesh
- 1:19Why We Should Talk about Data Mesh
- 9:05Domain Ownership
- 19:39Hard Limitations
related talks
38mData Mesh, Now
51mData Mesh – Successful with People, Process, and Technology
43mUntangling Data Mesh: A paradigm shift in Big Data
52mFrom Data Mess to Data Mesh: Navigating People, Process & Platforms
20mEmbracing Data Mesh: A Modern Strategy for Scalable Data Management
39mData Mesh: Why, What and How
13mData Mesh is a Big Idea: Take Your Team From Vision To Reality
34mBest and Worst Days of Data Mesh