database-migrations

Perform zero-downtime database migrations by applying an expand-contract strategy, separating schema changes from data migrations, and using non-blocking index creation to prevent table locks during rollout.

Yes, this database migration approach supports Prisma, Drizzle, Kysely, Django, TypeORM, and golang-migrate, coordinating safe reversible schema and data changes across these ORMs.

The best way to separate schema and data migrations is to split them into distinct steps with clear rollback paths, enforcing a migration safety checklist to prevent data loss.

Apply non-blocking index strategies in PostgreSQL by using concurrent index creation methods, which the skill enforces to avoid locking tables during schema changes and maintain zero-downtime.

Yes, you can reverse a schema change if a data migration fails because the skill enforces reversible migration paths and safety checklists to safely rollback database changes.

You need to separate schema changes from data migrations to maintain zero-downtime rollout, ensure safe reversibility, and prevent data loss caused by tightly coupled database updates.