Software Engineer at a tech vendor with 11-50 employees
Real User
Top 20
Jun 24, 2026
My main use case for Redgate Flyway is that it is a migration version control tool. I prefer Redgate Flyway because instead of manually running SQL scripts on different environments like dev, QA, and production, Redgate Flyway helps automate this process. It tracks which scripts have already been executed and only runs new migration scripts. It ensures every environment has the same database schema, which is very helpful for all the people on the team. It also keeps a history of database changes. In my first company, I used Redgate Flyway for a project where we were integrating MakeMyTrip APIs. In that particular project, we had to create a lot of tables, and I generally used Redgate Flyway for that. The main purpose of using it was that we had to make a lot of schema changes. Instead of doing it manually in the PostgreSQL database, we can use Redgate Flyway. What I did was version the file name, then provide the SQL language in that file, and run it. It keeps executing from there.
The main use case for Redgate Flyway is that previously we had to manually manage our different environment database scripts. We are using a .NET application with a Dapper back-end, and we have numerous SQL objects including stored procedures, views, table scripts, and DDL and DML scripts each time we deploy. We needed to manage scripts for the development environment, then for the staging environment, then for production, and that caused too much discrepancy and human effort during the release. After learning about Redgate Flyway, we started using it and have managed multiple environments within it. Redgate Flyway provides support for different branches, allowing us to manage our scripts with each script recorded with a version number. This has reduced the discrepancy in our deployments and accelerated our procedure significantly. The human effort required has become considerably less. Regarding how Redgate Flyway fits into my workflow, as a team, we always wanted to automate or record everything we do and maintain transparency. From the database side, we needed a tool that transparently shows what developers have done and what we will take to production deployment. Redgate Flyway aligned with our needs in this way. Our next target is to create pipelines for Redgate Flyway, but it is currently working well for us. We have set up different environments in Redgate Flyway and it is functioning properly. We have a repository on GitHub and we push and pull from there.
Business Development Manager at Ford Motor Company
Real User
Top 5
Apr 10, 2026
Redgate Flyway is my primary tool for database migrations, especially for solutions based on the Java programming language. A specific example of how I use Redgate Flyway for database migrations in a Java-based solution is that it has an intuitive way to operate within the Java ecosystem. It has multiple functions and events to monitor migration progress, making it very useful for solutions that have several migrations with breaking changes. In a short period of time, I can subscribe to each event during the migration and observe the entire progress, detect any problems, and add behaviors at any time. I use Redgate Flyway in every single environment. In my opinion, it is a very good tool for every scenario and is not restricted to development environments only.
Redgate Flyway delivers agile database migrations, optimizing version control and deployment workflow. Its approach is designed to align efficiently with DevOps practices, enabling teams to handle diverse database environments with precision and speed.Redgate Flyway offers robust migration tools adapted for flexible database configurations, integrating seamlessly into continuous delivery pipelines. Known for its consistent performance, Flyway simplifies complex database transformations,...
My main use case for Redgate Flyway is that it is a migration version control tool. I prefer Redgate Flyway because instead of manually running SQL scripts on different environments like dev, QA, and production, Redgate Flyway helps automate this process. It tracks which scripts have already been executed and only runs new migration scripts. It ensures every environment has the same database schema, which is very helpful for all the people on the team. It also keeps a history of database changes. In my first company, I used Redgate Flyway for a project where we were integrating MakeMyTrip APIs. In that particular project, we had to create a lot of tables, and I generally used Redgate Flyway for that. The main purpose of using it was that we had to make a lot of schema changes. Instead of doing it manually in the PostgreSQL database, we can use Redgate Flyway. What I did was version the file name, then provide the SQL language in that file, and run it. It keeps executing from there.
The main use case for Redgate Flyway is that previously we had to manually manage our different environment database scripts. We are using a .NET application with a Dapper back-end, and we have numerous SQL objects including stored procedures, views, table scripts, and DDL and DML scripts each time we deploy. We needed to manage scripts for the development environment, then for the staging environment, then for production, and that caused too much discrepancy and human effort during the release. After learning about Redgate Flyway, we started using it and have managed multiple environments within it. Redgate Flyway provides support for different branches, allowing us to manage our scripts with each script recorded with a version number. This has reduced the discrepancy in our deployments and accelerated our procedure significantly. The human effort required has become considerably less. Regarding how Redgate Flyway fits into my workflow, as a team, we always wanted to automate or record everything we do and maintain transparency. From the database side, we needed a tool that transparently shows what developers have done and what we will take to production deployment. Redgate Flyway aligned with our needs in this way. Our next target is to create pipelines for Redgate Flyway, but it is currently working well for us. We have set up different environments in Redgate Flyway and it is functioning properly. We have a repository on GitHub and we push and pull from there.
Redgate Flyway is my primary tool for database migrations, especially for solutions based on the Java programming language. A specific example of how I use Redgate Flyway for database migrations in a Java-based solution is that it has an intuitive way to operate within the Java ecosystem. It has multiple functions and events to monitor migration progress, making it very useful for solutions that have several migrations with breaking changes. In a short period of time, I can subscribe to each event during the migration and observe the entire progress, detect any problems, and add behaviors at any time. I use Redgate Flyway in every single environment. In my opinion, it is a very good tool for every scenario and is not restricted to development environments only.