Blue Green Deployment for a Monolith: Zero Downtime Without Data Loss
Learn how blue-green deployment works for a monolith, why the shared database is the real constraint, and how to switch, verify and roll back safely.
14 min read
Tag
Learn how blue-green deployment works for a monolith, why the shared database is the real constraint, and how to switch, verify and roll back safely.
14 min read
Learn how expand-contract migrations keep a shared schema compatible with two app versions in a blue-green deployment, and where rollback stops being safe.
14 min read
Learn how to keep a shared database compatible with both app versions during blue-green cutover, using expand/contract migrations and rollback rules.
14 min read
How to run blue-green deploys for a monolith on one shared database: expand/contract migrations, traffic switching, draining, rollback limits and a runbook.
14 min read
How to run blue-green deployments on a monolith: expand/contract migrations, externalized sessions, draining, and a rollback strategy set before cutover.
14 min read
Compare blue-green and rolling deploys for a single monolith: mixed-version safety, database migrations, traffic switch mechanics, rollback speed and cost.
14 min read
Learn how to run a blue green deployment monolith safely: backward compatible migrations, expand-and-contract, traffic switch timing and rollback windows.
13 min read
Compare blue-green and rolling deploys for a stateful monolith on one database: schema compatibility, rollback limits, sessions, jobs and connection costs.
15 min read