Flyway - Enabling DB-migrations-as-code
Overall Satisfaction with Flyway
We use Flyway to manage and apply DB migration patch scripts. It's also used as part of the automated test suites to verify that the changes in the PR are good and would be applied successfully. In other words, we use Flyway to test the patch scripts prepared by the engineers before merging them to main branch.
Pros
- Manage DB migration patch scripts
- Apply DB migration patch scripts
- Test DB migration patch scripts
- Setup new DB instances, including on local env
Cons
- GUI could be more user friendly
- Applying patch scripts on a blank DB differs from on a DB with data, so the migration could still fail when all tests passed
- Configurations options could be more flexible / powerful
- Maven / Gradle integration
- Sanity check test with automated test suites
- Clear status report, error messages
- DB migration is fully automated
- DB migration is committed to source code, repeatable on all environments
- DB migration is fully integrated into development cycle
Do you think Redgate Flyway delivers good value for the price?
Yes
Are you happy with Redgate Flyway's feature set?
Yes
Did Redgate Flyway live up to sales and marketing promises?
Yes
Did implementation of Redgate Flyway go as expected?
Yes
Would you buy Redgate Flyway again?
Yes
Comments
Please log in to join the conversation