Data Mesh In Practice – How To Set Up A Data Driven Organization
summary
Case study-backed guidance on rolling out Data Mesh: pilot a simple data product (finance is a good candidate) over about three months, iterate infrastructure as products, and shift pipeline work into domains while keeping a central enablement team for tooling. Track usage metrics (they even tie to usage-based payments) and use interoperability (Hive metastore or Starburst-style virtualization) to avoid metadata sprawl. Cautionary results: overloaded central teams stall work for weeks but a focused cross-team session can resolve issues in ten minutes.
AI-written summary · about
chapters (7)
- 0:00Introduction and context
- 1:56Data mesh concepts
- 6:57Real-world collaboration
- 13:58Adoption strategies
- 18:05Scaling and infrastructure
- 24:05Selecting technology
- 27:51Pitfalls and best practices
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
43mWhen design meets data: Using Data Mesh for a consumer and business-driven data strategy
20mEmbracing Data Mesh: A Modern Strategy for Scalable Data Management
13mData Mesh is a Big Idea: Take Your Team From Vision To Reality
34mBest and Worst Days of Data Mesh
43mUntangling Data Mesh: A paradigm shift in Big Data
