Flyway Migration Authoring and Deployment

A migration is a committed, ordered, permanent fact about the schema. Write it so an operator can run it on a restored copy, understand it without the application, and reverse it when reversal is honestly possible.

When to use

• Naming or authoring a versioned, repeatable, or undo migration, or handling a checksum mismatch or a database with a schema but no history.
• Planning a zero-downtime expand-and-contract change with dual write, backfill, and cleanup.
• Deciding between startup migration and a pipeline step, or seeding reference data and protecting migration-only credentials.

When not to use

• Choosing column types, index types, or query plans: hand off to spring-boot-postgresql.
• Updating entity mappings for the new column: hand off to spring-boot-hibernate.
• Pipeline stage ordering, gates, and promotion: hand off to spring-boot-ci-cd.
• Provisioning a throwaway test database: hand off to spring-boot-testcontainers or spring-boot-integration-testing.

Ownership and sibling boundaries