Migrating to Microservice Databases
summary
Claims concrete steps for moving a relational monolith to microservice-owned databases: break schema changes into tiny, back-and-forward compatible migrations (one SQL per deploy), shard long updates to avoid locks, rename columns via staged add/copy/switch/delete, drop constraints only after migration. Recommends automation with Flyway and Liquibase, explains zero downtime migrations, compares CQRS, event sourcing and materialized views, lists 9 strategies for integration and highlights log-based replication with Debezium CDC for legacy systems.
AI-written summary · about
chapters (17)
- 0:00Start
- 2:55"Now, every company is a software company" -Forbes
- 5:14DevOps & Microservices
- 11:30Maintenance Window
- 12:34Deployment
- 14:30Code is easy, state is hard
- 15:46my relational database?
- 16:21Zero Downtime Migrations
- 16:42Back and Forward Compatibility
- 16:59Baby Steps Possible Batch Size
- 17:20Too many rows = Long Locks
- 17:36Shard your updates
- 23:33What about referential integrity constraints?
- 25:19Extracting your Microservice database
- 26:59Splitting is not easy, but how do I integrate later?
- 31:03CRUD & CQRS
- 33:43CQRS & Event Sourcing
related talks
01h 05mMigrating to Microservice Databases: From Relational Monolith to Distributed Data
58mDatabases in the Microservices World
30mDatabases in the Microservices World
54mFrom a distributed monolith to a microservices solution
27mHow Micro-Service Patterns Change When the Database Scalable
47mHow to Choose a Right Database for Your Microservices?
46mData in a Microservices world from conundrum to options
31mMonolith to Microservices: A Guide to Seamless Transitions