Shift Left Data Quality with Data Mesh Principles
summary
Argues that adopting domain ownership, data as a product, self-serve platform and federated computational governance shifts quality left by making producers own analytical data, publish freshness/lineage/availability SLAs, and supply machine-readable quality rules. Describes building self-serve platform capabilities that automatically apply domain rules, call out bad records, and enforce mesh-level standards so fixes happen at the source (cheapest) rather than downstream, and reports that this increases trust and reuse across large organizations.
AI-written summary · about
chapters (5)
- 0:00Start
- 1:25Data quality - the problem space
- 5:52Centralized structures create bottleneck
- 8:36What is Data Mesh?
- 9:10Principles of Data Mesh
related talks
01h 02mShift Data Quality Left with Data Mesh Principles
29mHow to treat your data as a product
01h 00mData Mesh: Beyond the Data Lake
43mUntangling Data Mesh: A paradigm shift in Big Data
51mData Mesh – Successful with People, Process, and Technology
52mFrom Data Mess to Data Mesh: Navigating People, Process & Platforms
39mData Mesh: Why, What and How
41mWhat is a Data Mesh - And How Not To Mesh it Up