skill-database-migration

Zero-downtime database migrations use an expand-contract pattern, separating schema changes from data backfills into staged deployment workflows. This approach applies safe operations incrementally, ensuring production rollout proceeds without locking tables or interrupting active traffic.

Managing database migration rollbacks requires providing reliable down migrations and keeping migration steps small and focused. Testing on staging before production and backing up databases ensures you can safely revert schema changes if deployment encounters issues.

Yes, this database migration guidance covers Prisma Migrate, Alembic, TypeORM, and Flyway. It provides tool-specific scope and end-to-end workflows for applying safe schema changes across these popular frameworks.

Data backfill during schema migrations should be handled in separate scripts, independent of the core schema changes. The deployment workflow uses an expand-deploy-cleanup pattern, applying backfills safely before completing the final rollout phase.

Idempotent database migrations ensure consistent execution across environments without unintended side effects. Avoiding altering already-run migrations on shared environments prevents schema drift and maintains integrity across the deployment pipeline.