Redgate Flyway Reviews and Ratings

Use Cases and Deployment Scope

We use it as the primary tool for database migrations, especially for solutions based on Java programming language. It has an intuitive way to operate within the Java ecosystem (Maven and Gradle especially). It has multiple functions/events to keep watch on the migration progress, so it's very useful for solutions that had several migrations with breaking changes on it, in a small period of time, you can subscribe to each event along the migration and see the whole progress of it, and detect any problems or odd behaviors at any time.

We use Flyway in every single environment, in my opinion, is a good tool for every single scenario and is not restrained to development environments only. I do think that you will need at least the Team edition, to take advantage of database objects as code on version control. This feature has a huge impact on the software development cycle as it works as a kind of ORM tool with also the migration capabilities.

Likelihood to Recommend

Database Migrations on Java-based solutions. It has one of the best integrations with it as a database migration tool, you can do it with the community edition (no pricing involved) and it works flawlessly with Maven and Gradle. It's not an expensive tool in order to use the next level of features and is worth the money. I would recommend reaching that edition level as the object mapping feature gets really handy. I would not recommend it for any Microsoft-based solution (.Net) as is not compatible at all based on my experience, this is a tool only worth it with Java applications.

Use Cases and Deployment Scope

When new features are developed for applications they sometimes also require changes to the underlying database. These changes would be very difficult and time consuming to apply to all environments where application is running if had to done manually. Flyway can help to automatize this process and save time for employees.

Likelihood to Recommend

If your application is running on many environments then some kind of automation for database migrations should be implemented. This will save time and trouble for employees and helps to manage migrations. However it must be understood that it is not a magical tool & should be studied properly so that it's limitations are understood & it will be used properly. Otherwise it might cause problems to the application.

Use Cases and Deployment Scope

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.

Likelihood to Recommend

With good Maven / Gradle integration, Flyway is very well suited to be part of a software project, from the very beginning to real production migration. The concepts are simple enough so all engineers in the team can use it at a basic level. The troubleshooting capabilities are reasonably good to troubleshoot migration issues. The ability to test out the migration patch scripts as part of the automated test suites on PR is also very great, although not perfect.

Use Cases and Deployment Scope

Database version control can be challenging, and we were facing issues while managing version controls for our database. Flyway helped us improve this significantly by reducing our risk of data loss and allowing automatic backups for the database. We had better peace of mind and reliability after we started using Flyway for our databases.

Likelihood to Recommend

We're thoroughly satisfied with Flyway. Even someone with basic SQL knowledge could use it without getting into tech complexity. It eased our release management and DevOps process while also increasing reliability. We use it across our testing, staging, and production environments. It is a perfect fit for our continuous delivery and zeroes downtime pipeline.