Databases in the Microservices World
summary
Argues for treating each microservice as owner of its micro-database and automating provisioning, authentication and backups so dozens of heterogeneous datasources behave like one managed fleet. Recommends using event store events to populate local views instead of cross-service joins, shows a concrete pattern where a dedicated customer service issues primary keys and other services store local customer profiles with a foreign key. Advises DBaaS for uptime and to default to SQL unless another store matches the workload.
AI-written summary · about
chapters (20)
- 0:00Introduction and speaker intro
- 1:33Why microservices and databases
- 3:40Monolithic database pitfalls
- 5:48Bounded contexts in databases
- 7:33Introducing micro databases
- 8:55Customer record ownership
- 11:27Database type optimization
- 12:30SQL database deep dive
- 16:04Document databases explained
- 18:31Graph databases overview
- 19:34Key-value databases
- 20:39Time series databases
- 21:24Text search databases
- 23:09Object stores and blob storage
- 24:12Event sourcing databases
- 25:15Column store databases
- 25:59New SQL databases
- 27:28Hybrid database options
- 28:32Automation for micro databases
- 29:35Recommendations and conclusion
related talks
58mDatabases in the Microservices World
51mData management in a Microservices world
47mHow to Choose a Right Database for Your Microservices?
47mMigrating to Microservice Databases
31mHarness the Power of a Single Database for Microservices
27mHow Micro-Service Patterns Change When the Database Scalable
44mHow to Serve Thousands of Databases from One Microservice Without Losing Your Mind
01h 05mMigrating to Microservice Databases: From Relational Monolith to Distributed Data