database-migrations

The expand-contract pattern separates schema changes into expand phases that add new structures and contract phases that remove old ones, enabling zero-downtime database migrations without locking tables or breaking running application code.

Safe schema changes and rollbacks in PostgreSQL require reversible UP and DOWN migrations, separating data migrations from schema migrations, and applying expand-contract workflows to ensure auditable, zero-downtime deployments.

Yes, the database migration approach applies to common ORMs including Prisma, Drizzle, TypeORM, and Django, providing safe migration patterns and enforcing UP/DOWN rules and expand-contract workflows across these tools.

Separating data migrations from schema migrations prevents locking conflicts and application errors during deployment, allowing schema changes to execute safely first while data backfilling occurs independently under zero-downtime constraints.

The best way to handle risky production database migrations is enforcing safety rules such as UP/DOWN reversibility, separate data and schema migrations, and expand-contract deployment workflows using tooling like golang-migrate for auditable changes.

Zero-downtime migrations using expand-contract are unsuitable when immediate, destructive schema changes are required or when the application cannot support backward-compatible deployment phases needed for safe, reversible transitions.