How to Split a Monolith Database Gradually Without Breaking Joins
Learn how to split a monolith database by mapping joins first, assigning table ownership, and migrating one reversible stage at a time with safe rollbacks.
15 min read
Tag
Learn how to split a monolith database by mapping joins first, assigning table ownership, and migrating one reversible stage at a time with safe rollbacks.
15 min read
Learn when to join data across microservices at request time with API composition or ahead of time with CQRS read models, and what each costs to run.
16 min read
Split a shared database by separating ownership first: map coupling, isolate schemas, pick CDC, outbox or dual writes, then cut over with rollback at each step.
14 min read
Design a modular monolith database in PostgreSQL: schema per module, enforced data ownership, cross-module foreign keys, safe cross-module queries and migrations.
14 min read
Learn what database per service means, why shared databases break microservices, and how sagas, outboxes and read models handle the costs it brings.
14 min read
Learn how to design a modular monolith: drawing module boundaries, enforcing data ownership and dependency rules in CI, testing, and when to extract services.
13 min read