database-migrations

Zero-downtime database migrations separate schema changes from data transformations and apply safety checks to avoid locking tables. This approach ensures production databases remain fully operational during upgrades using Alembic, Django, or raw SQL.

The safest way to plan a database rollback is to enforce forward-only production migrations while maintaining a dedicated rollback plan. This Skill provides templates and guidance for creating reversible migrations and testing rollback strategies.

Yes, this guidance supports Alembic, Django ORM, and raw SQL workflows. It provides specific zero-downtime patterns, safety checklists, and best practices tailored to each environment for production-grade projects.

Separating schema changes from data migrations prevents database locking and data loss during production updates. This separation allows you to apply backward-compatible schema updates before removing old columns or transforming data.

You audit your migration strategy by running a comprehensive safety checklist covering upgrades, data migrations, and rollback plans. This Skill helps review existing changes and generate a safe, zero-downtime plan for your next schema update.

You should avoid backward-incompatible database migrations in production environments where downtime and data loss are unacceptable. This Skill enforces safety checks and forward-only patterns to ensure schema changes remain reversible.