How to Choose a Right Database for Your Microservices?
summary
Microservices require choosing a database by concrete needs not buzzwords: whether a service is stateful or stateless, needs strong transactions will be committed semantics, must work without internet or at high scale, and whether teams expect independent deployable units. The uploader cites roughly 5500 production applications and small codebases like "512 company" examples to show migration and per-service data models matter; pick relational for ACID workflows, key‑value or document stores for local scale and offline sync.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 8:58Monolithic vs microservices
- 16:31Database challenges in microservices
- 25:03Choosing the right database
- 33:14Database types overview
- 41:27Recommendations and summary
related talks
58mDatabases in the Microservices World
30mDatabases in the Microservices World
47mMigrating to Microservice Databases
51mData management in a Microservices world
25mBuilding Modern Applications with Custom Databases
44mHow to Serve Thousands of Databases from One Microservice Without Losing Your Mind
01h 05mMigrating to Microservice Databases: From Relational Monolith to Distributed Data
50mMicroservices for Mortals