Harness the Power of a Single Database for Microservices

on YouTube ↗31m

" summary

Argues that multiple microservices can share a single SQL database when using modern relational and distributed SQL features to isolate workloads and maintain consistency. Recommends using Yugabyte (Postgres-compatible) or similar distributed SQL that offers active-every-node distributed SQL, rolling upgrades, and multi-region replication so failures don’t force database splits. Describes concrete controls: table spaces mapped to regions, row-level security, schemas, online DDL and different APIs (Postgres and Cassandra-like) and warns schema changes and operational sprawl still drive splits.

AI-written summary · about

" chapters (6)

1. 0:00Introduction to microservices and databases
2. 2:35Problems with databases in microservices
3. 9:13One database per microservice trade-offs
4. 13:55What counts as a database
5. 24:14Distributed SQL databases benefits
6. 30:43Key takeaways and Q&A

" related talks

• 47mHarness the Power of a Single Database for MicroservicesFranck Pachot · JCON Europe 2023
• 26mNewSQL: concepts, realities and when you should embrace itGargi Ahluwalia · XConf Australia 2022
• 30mDatabases in the Microservices WorldRob Richardson · Berlin Buzzwords 2021
• 58mDatabases in the Microservices WorldRob Richardson · Developers Summit 2021
• 47mMigrating to Microservice DatabasesEdson Yanaga · Oredev 2017
• 08mScalable GraphQL Applications Powered by Cloud-ready Distributed SQL DatabaseNikhil Chandrappa · GraphQL Galaxy 2021
• 01h 05mMigrating to Microservice Databases: From Relational Monolith to Distributed DataEdson Yanaga · NDC Porto 2019
• 27mHow Micro-Service Patterns Change When the Database ScalableBrecht De Rooms · Scale By the Bay 2020