Databases in the Microservices World
summary
Argues for breaking a monolithic schema into bounded contexts and then into micro-databases that each one service owns, with events published to an event bus (Kafka or ESB) so consumers keep local read models instead of cross-service joins. Surveys concrete choices — SQL, document, graph, key‑value, time‑series, text search, columnar, object stores, event sourcing and NewSQL — and recommends automation and use a database as a service for provisioning, backups and auth before splitting data.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 2:27Microservices and data ownership
- 8:36Breaking monolithic databases
- 18:59Database types overview
- 39:37Event sourcing and analytics
- 51:49Handling duplicate data
- 57:50Q&A and conclusion
related talks
30mDatabases in the Microservices World
51mData management in a Microservices world
47mHow to Choose a Right Database for Your Microservices?
47mMigrating to Microservice Databases
25mBuilding Modern Applications with Custom Databases
31mHarness the Power of a Single Database for Microservices
01h 05mMigrating to Microservice Databases: From Relational Monolith to Distributed Data
44mHow to Serve Thousands of Databases from One Microservice Without Losing Your Mind