All articles

Schema

Zero-Downtime Migrations: Expand and Contract

Oct 14, 2026 migrations · zero downtime · ddl · deployment

The deployment discipline that lets schema changes ship during business hours — because every step is additive first.

Downtime is usually manufactured, not required. A column rename that breaks the running release, a migration that locks a table the app is serving, a backfill that saturates I/O — these are sequencing errors, and sequencing is a solvable problem.

The expand-and-contract pattern is the solution the industry keeps rediscovering.

Expand: make the change additive

Deploy the new column, table, or index while the old path still runs. Nothing breaks because nothing is removed. Old code and new code both have everything they need — this is the moment your release becomes reversible.

Contract: only when nothing needs the old shape

Switch reads and writes over, verify with live metrics, then — in a later release — drop the old column. The delay between expand and contract is your safety margin. Teams that skip it are the ones scheduling 3 a.m. maintenance windows.

Tags

migrations zero downtime ddl deployment

Related articles

Work with Burj

Your database deserves engineering, not guesswork.

Tell us what is slow — CPU, queries, migrations, or cost — and we will scope the smallest safe fix.

Plan an engagement