The Realities Of Data Mesh – How To Drive Value And Engagement From Your Data Products
summary
Panel argues that practical steps beat buzz: start with a measurable business use, prove value with a small data product, and avoid federating too fast or losing specialist disciplines. Channel 4-style conceptual model provides a few common entities to enable reuse; RAF’s Wyvern implementation uses heavy coaching while domains mature. Governance requires a seismic rethink, and technology choices prioritize discoverability/cataloging plus openness and interoperability to let products combine and actually deliver value.
AI-written summary · about
chapters (7)
- 0:00Introduction and panel setup
- 3:52Data mesh as a decentralization journey
- 11:37Defining data products and ownership
- 17:22Cross-domain data entities and interoperability
- 21:54Balancing governance and innovation
- 26:29Technology criteria for data mesh
- 28:54Key takeaways and Q&A summary
related talks
23mHow To “Data Mesh”: What You Need To Know To Make It Real
43mWhen design meets data: Using Data Mesh for a consumer and business-driven data strategy
51mData Mesh – Successful with People, Process, and Technology
52mFrom Data Mess to Data Mesh: Navigating People, Process & Platforms
43mUntangling Data Mesh: A paradigm shift in Big Data
29mHow to treat your data as a product
38mData Mesh, Now
34mBest and Worst Days of Data Mesh