Data Divide: End User’s Cloud Native Journey to Distributed Databases
summary
Mastercard runs 2500+ databases across six engines and sees 5,000+ alerts per month, so the push is to stop bespoke schemas and offer a standard data service catalog that bakes in monitoring, logging and lifecycle controls. Platform teams build architecture, support and automation to let apps consume APIs with one pattern for on‑prem, cloud or hybrid. A prototype data mesh control plane with abstract data definitions exists but is early—culture, governance and measurable business outcomes decide adoption, not a single new database product.
AI-written summary · about
chapters (10)
- 0:00Intro
- 1:11CNCF Cloud Native
- 1:51Distribution of Database Services
- 3:35Database Infrastructure Capabilities Breakdown
- 4:26Distributed Database Focus Areas
- 5:48for Cloud Native Developers?
- 9:40for platforms and infrastructure teams
- 13:15Culture Culture Culture
- 18:05Distributed Database Analysis Efforts
- 22:14Questions?
related talks
32mCloud-Native Data: What is it? - Majors, Dunlap, O’Grady, Richardson, Drewitz
35mCloud Native Data Platforms - The why, what and how
44mData Mesh: Lessons from the trenches
36mIntroducing Data Mesh A Paradigm Shift In Analytical Data Management Architecture
10mpresent role and future
23mData Mesh Architecture in Banking
55mThe Great Data Debate 2022
57mOur DataMesh Journey: data architectures for microservices