database-migrations

Zero-downtime database migrations require separating schema changes from data migrations, applying expand-contract patterns, and enforcing non-blocking index changes to ensure reversible deployments without disrupting production traffic.

The expand-contract pattern expands the database schema first to support both old and new versions, then contracts by removing deprecated columns after application deployment, ensuring safe zero-downtime data backfills and reversible schema changes.

Yes, these migration patterns apply cross-stack to Prisma, Drizzle, Kysely, Django, and golang-migrate, providing safety guardrails and schema coordination across multiple database engines and ORMs.

Safe data backfills during database migrations involve batching data transformations independently of schema changes, avoiding long table locks, and maintaining rollback readiness to prevent production incidents on large datasets.

Blocking index changes lock database tables during creation, causing production downtime; non-blocking index changes must be enforced to avoid locking issues and minimize migration risk on live systems.

Separating schema migrations from data migrations isolates failure points, enables independent rollback for each phase, and enforces safety guardrails that prevent irreversible data loss during complex cross-ORM database deployments.