database-migrations

Perform zero-downtime database migrations by applying the expand-contract strategy, separating schema and data migrations, and using non-blocking operations across PostgreSQL and MySQL. This approach maintains application availability while schema changes are applied.

The expand-contract strategy for schema changes incrementally broadens the database structure before removing old parts. It separates schema and data migrations to deploy non-blocking updates safely, enabling reliable rollback plans.

Yes, this database migration approach works with Prisma, Drizzle, Kysely, Django, TypeORM, and golang-migrate. It provides explicit UP and DOWN handling alongside tooling patterns tailored for these specific ORMs.

Handle rollbacks when a database migration fails by defining explicit UP and DOWN migrations and testing against representative datasets. Robust rollback plans ensure schema changes and data migrations revert safely without downtime.

The best way to separate data migrations from schema changes is to define distinct migration safety guidelines and explicit UP and DOWN workflows. This isolation prevents locking conflicts and enables zero-downtime rollouts across multi-DB environments.

Avoid non-blocking operations during database migrations when executing complex data backfills that require strict transactional consistency. In these cases, separating schema and data migrations ensures safe execution without risking deployment integrity.