Rethinking Master Data Management With Data Mesh
summary
Argues that Data Mesh forces a rethink of MDM: move from centralized consolidation to a federated model where domains own data products with SLOs, linked by global identifiers and semantic registries. Uses a fashion retailer example where design, sourcing, logistics and sales each require different product attributes, showing mandatory centralized fields break quality. Recommends multiple contextual canonical models, provenance-aware linking (knowledge graph/ontology), and platform-enforced governance rather than a single source of truth.
AI-written summary · about
chapters (7)
- 0:00Introduction and background
- 2:07What is data mesh?
- 7:30Domain-driven design basics
- 13:09Master data management overview
- 20:12Example: Product data in retail
- 25:45Data mesh for master data
- 28:14Mindset shifts and conclusion
related talks
50mData Mesh: the new paradigm for data management
20mEmbracing Data Mesh: A Modern Strategy for Scalable Data Management
43mUntangling Data Mesh: A paradigm shift in Big Data
51mData Mesh – Successful with People, Process, and Technology
36mData Mesh and Its Superpowers
41mWhat is a Data Mesh - And How Not To Mesh it Up
36mIntroducing Data Mesh A Paradigm Shift In Analytical Data Management Architecture
38mData Mesh, Now