database-migrations

Zero-downtime database migrations use the expand-contract pattern: add a nullable new column, backfill data, switch reads to the new column, then remove the old one. This minimizes production lock time and ensures safe schema changes.

The expand-contract pattern adds a nullable new column, backfills existing data into it, switches application reads to the new column, and finally removes the old one. This ensures reversible schema changes without disrupting production traffic.

Handle database rollbacks using UP/DOWN migration patterns to reverse schema changes. The approach enforces migration safety checks and requires an explicit rollback plan for irreversible changes, ensuring you can revert any failed deployment safely.

Yes, this approach works with Prisma, Django, TypeORM, Drizzle, Kysely, and golang-migrate. It provides specific tooling guidance, practical workflow examples, and best-practice checklists for executing safe migrations across these ORMs.

The best way to separate schema changes from data migrations is to place data backfills into dedicated migrations. This isolates risks, enforces migration safety checks, and provides clear rollback plans for each distinct operation.

You should avoid irreversible database migrations whenever possible by using UP/DOWN patterns. If a migration must be irreversible, the process requires an explicit rollback plan and safety checks to ensure production database stability.