BoF: Data Mesh Community of Practice: What It Is, Why It's Hard, and How to Help...
summary
Claims that data volumes grow 63% monthly and organizations ingest from 400 data sources per org; executives report 9/10 find preparing data hard and only 13% of ML models reach production. Recommends AWS Glue + Lake Formation + Athena as a real-world data mesh stack (JPMorgan case) and cites Brainly as a public diary of adoption. Argues for federated governance that automates standards, notes ownership, cost, and the need for multiple data stewards as the main barriers.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 3:31Data governance importance
- 4:34Data mesh concept
- 6:19Data mesh challenges
- 8:47Domains in data mesh
- 10:34AI in data governance
- 14:04Real-world implementations
- 17:59Open data and privacy
- 22:37Warehouses vs data lakes
- 25:04Data mesh for startups
- 28:57Automating data tagging
- 31:47Federated data access
- 34:15Geospatial data challenges
- 36:43Data ownership roadblocks
- 38:09Cultural governance challenges
- 39:13Branding in regulated industries
- 41:43Shared data catalogs
- 42:46Governance buy-in
- 43:07Closing remarks
related talks
23mHow To “Data Mesh”: What You Need To Know To Make It Real
31mData Mesh In Practice – How To Set Up A Data Driven Organization
47mModern Data Architecture: Breaking the Big Data Monolith
20mEmbracing Data Mesh: A Modern Strategy for Scalable Data Management
49mBuild modern data architecture and data mesh patterns on AWS
51mData Mesh – Successful with People, Process, and Technology
47mData Mesh - a hot air balloon?
48mData Mesh Paradigm Shift in Data Platform Architecture -