Data Mesh vs Data Fabric - in Microsoft Fabric
summary
Microsoft Fabric claims to let organizations implement Data Mesh by centralizing storage in OneLake, grouping workspaces with the domains feature, and exposing reusable semantic models as certified outputs, while using Data Activator for monitoring and Copilot for augmentation. The built-in Data Hub catalog is rudimentary and full catalog functionality requires Purview; knowledge graphs and MDM are missing. A demo shows lineage, certified assets, security labels, and an environment where only ~10% of pipelines are endorsed.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 1:14Agenda
- 1:43Data mesh explained
- 3:59Data mesh domains
- 5:59Federated governance
- 9:06Self-serve platform
- 10:39Data mesh benefits and risks
- 14:00Data fabric defined
- 15:43Data fabric architecture
- 18:40Data fabric advantages
- 20:08Data mesh in Fabric
- 23:11Trust in Fabric products
- 24:26Fabric implementation limitations
- 27:00Domains in Microsoft Fabric
- 29:07Governance in Fabric
- 30:45Fabric as a platform
- 31:42Implementing data fabric
- 34:29Demo: Domain setup
- 35:15Demo: Domain management
- 38:12Demo: Data hub and lineage
- 40:54Demo: Purview hub
- 42:32Conclusion
related talks
20mData Fabric or Data Mesh - Similarities, Differences & Optimal Possible Combination of Both
20mData Mesh, Data Fabric & Co - the End of Monolithic Architecture Concepts?
19mAccelerate your data potential with Fabric
22mA Microsoft Hybrid Approach to Data Mesh and Data Fabric
27mModernize your data integration to enable petabyte scale analytics with Microsoft Fabric
50mMicrosoft Fabric Data Factory Q&A
46mMicrosoft Fabric Synapse data warehouse Q&A
44mUnify your data with OneLake and Microsoft Fabric