backend-migrations

Guides on handling backend migrations with adherence to coding standards.

• Handles backend database schema changes.
• Ensures consistency across migration files.
• Follows defined coding standards for migrations.
• Maintains version control and rollback safety.

• Migrations must be atomic and idempotent.
• Use standard naming conventions for files.
• All changes must be tested in staging first.
• Migrations must include rollback logic.
• No manual database changes allowed.
• Must document each migration clearly.
• Must be version-controlled and reviewed.
• FORBIDDEN: modifying DB directly in code.

1. 1.Identify the required database change.
2. 2.Write a migration file following naming and structure standards.
3. 3.Test the migration in a non-production environment.
4. 4.Review and approve the migration with team.
5. 5.Apply in production only after approval and testing.