database-migrations

Zero-downtime database migrations require separating schema changes from application deploys, using techniques like expand-contract patterns to update production systems without service interruption. This Skill provides strategies for seamless schema updates and rollback procedures.

Safely adding a column to a large database table involves adding it as nullable or with a default value, backfilling data in batches, and avoiding long table locks. This Skill covers schema evolution patterns for large production SQL databases.

Yes, this database migration guidance supports both PostgreSQL and MySQL, covering specific patterns for safely managing schema changes and data transformations across various SQL databases.

Yes, these migration patterns integrate with ORM tooling including Prisma, Drizzle, Django, TypeORM, and golang-migrate, addressing specific migration tooling and transactional integrity for each framework.

Database rollback strategies ensure reversibility for all migration steps by applying compensating schema changes and data backups before destructive operations. This Skill provides patterns for safe schema evolution and reliable rollback execution.

Zero-downtime schema changes are limited by operations requiring exclusive table locks, such as altering column types or adding constraints on large tables. This Skill outlines safe schema evolution patterns and when to use multi-step deployments to avoid these constraints.