database-migrations

Zero-downtime database migrations use the expand-contract strategy to separate schema and data changes into backward-compatible deployment phases. This approach batches concurrent operations to safely add, alter, or remove schema elements without blocking production traffic.

The expand-contract pattern for PostgreSQL schema changes splits migrations into expand phases that add new columns or tables, and contract phases that remove deprecated elements. This allows application code to deploy and adapt across services without breaking backward compatibility.

Yes, this guidance supports major ORM frameworks including Prisma, Drizzle, Django, TypeORM, and golang-migrate. It provides tooling guidance and structured patterns for adding, dropping, and renaming schema elements specific to these frameworks across PostgreSQL and MySQL.

The best way to handle data backfills during schema migrations is through batched operations deployed separately from schema changes. By structuring data migrations independently and applying a migration safety checklist, you backfill production data with minimal risk and zero downtime.

A migration safety checklist for MySQL schema changes should be used for any production deployment involving column alterations, table renames, or data backfills. It enforces guardrails by verifying backward-compatible approaches, batching, and concurrent operation safety before execution.

Schema renames require backward-compatible approaches in production to prevent service disruptions during rollout. By using expand-contract strategies to create new columns or tables before removing old ones, you ensure environments and services can migrate without downtime.