backend-migration-standards

Create reversible, one-change-per-migration files with clear naming and zero-downtime safety.

• Manage database schema changes via migration files
• Ensure reversibility with down methods for every up migration
• Separate schema and data changes in distinct files
• Apply naming conventions for clarity and versioning

• Reversibility is Mandatory
• One Logical Change Per Migration
• Never Modify Deployed Migrations
• Use timestamps and descriptive names in migration files
• Index with concurrent creation on large tables
• Data migrations must be idempotent and batched
• Additive changes first, then remove old columns
• Test migrations up/down with production-like data

1. 1.Create migration file with timestamp and descriptive name
2. 2.Ensure every migration has a working rollback method
3. 3.Keep schema and data changes in separate files
4. 4.Use concurrent index creation for large tables
5. 5.Test migration up and down before committing
6. 6.Run with anonymized production data for validation