Data Mesh Architecture in Banking
summary
Argues that banking must move analytics ownership into business domains, backing it with four concrete principles: data domain ownership, data as a product, a self-serve platform and federated governance. Recommends CQRS pattern to keep OLTP performant while producing read-optimized copies, cites infra-as-code so a sandbox spins up in 5 minutes, and describes a built data marketplace at ABN Amro where domains publish, rate and subscribe to data products. Warns of initial data redundancy, licensing costs and implementation complexity.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:20Agenda
- 1:15Architecture History
- 3:00Data Mesh Architecture
- 5:28What is Data Mesh
- 6:50Data Mesh Journey
- 7:35Data Domain Ownership
- 10:10CQRS
- 11:10Data as Product
- 12:16People
- 13:14Scaling
- 16:25Federated Governance
- 20:49Challenges
related talks
01h 00mData Mesh: Beyond the Data Lake
39mData Mesh: Why, What and How
51mData Mesh – Successful with People, Process, and Technology
01h 02mShift Data Quality Left with Data Mesh Principles
36mIntroducing Data Mesh A Paradigm Shift In Analytical Data Management Architecture
47mModern Data Architecture: Breaking the Big Data Monolith
36mData Mesh and Its Superpowers
20mEmbracing Data Mesh: A Modern Strategy for Scalable Data Management