.svg){kind=icon}
Find the solution that's right for you
Contact us for a limited-time, special offer when you choose or switch to Liquibase.
Liquibase vs. Flyway
How does Flyway (Redgate) stack up against Liquibase?
Find out which database DevOps tool is right for you.
Get the Comparison Guide
Database change
management tools
Liquibase and Flyway are both open-source database migration tools popular for versioning, deploying, and tracking database changes. Both offer:
Premium & Community
Foundational community (free) and advanced premium (paid) versions
Extending CI/CD
Capabilities to extend CI/CD to the database change workflow
Migration
A migrations-based approach to database changes
Liquibase helps you bring DevOps to the Database
Supports the broadest set of databases with advanced features
Work from where you want and meet up with your colleagues somewhere new each quarter.
More Flexibility
More flexibility in your database changes with artifact-based deployments
More Control
More control over execution updates and batch releases
Simple
Enables you to standardize best practices and simplify repeatable actions
DevOps Metrics
Improves database observability with DevOps metrics for your pipeline
Comparing Liquibase & Flyway
Flyway | Liquibase | |
|---|---|---|
FEATURES | ||
Supported databases | 51 Relational Databases and Data Warehouses | 60 Relational Databases, Data Warehouses, and NoSQL Databases |
Change definitions and ordering changes | Numbered SQL Files | Rearrangeable ChangeLogs (SQL, XML, JSON, or YAML) |
Changes are not applied to environments where the changes are already present | ||
Programmatically skip or batch changes by creating subsets of changes to apply | ||
Control the execution of an update based on the state of the database | ||
Dry runs | $ | |
Create multi-step Workflows to standardize best practices, simplify actions, and improve governance and control | ||
Allow Rollbacks to undo a database change | $ | |
Target, or cherry pick, a change or set of changes to roll back | $ | $ |
Validates database code against predefined rules set by DBAs on-demand or in automation | $ | $ |
Compare the state of two databases to detect drift or malicious code | $ | $ |
Java-based migrations | ||
Migrations with Spring Boot | ||
Measures and provides database DevOps metrics for your pipeline |
Scale and expand with the broadest database support
Liquibase’s proactive approach and massive community support means more databases—and more diverse databases, including NoSQL—to cover your needs today and tomorrow.
Watch On-Demand Demo
.svg){kind=icon}
.svg){kind=icon}
Update, manage,
and deploy changes with ease
Flyway offers linear versioning using filenames for change deployments, which causes tedium as things need to change. Liquibase uses artifact-based deployments with ChangeLogs, which are collaborative, rearrangeable sets of changes.
.svg){kind=icon}
Control the execution of updates and batch releases
Liquibase makes it easy to skip or batch changes by creating subsets of change with Labels and Contexts. With Preconditions, you can control the execution of an update based on the state of the database.
.svg){kind=icon}
Improve governance by standardizing best practices
Customize and automate multi-step workflows to enable simple, repeatable actions.
.svg){kind=icon}
Database observability to monitor DevOps metrics
Liquibase’s unique Structured Logs make it easy to bring database change and deployment metadata to your DevOps dashboards to enable continuous improvement for your databases.
See why the database DevOps community trusts Liquibase
“Liquibase is much more powerful compared to Flyway since it is much more flexible in nature.”
Kunnath Rahul
Software Engineer
Enterprise Software Company
“Comparing Liquibase and Flyway, I found Liquibase to be easier to learn and faster to implement than Flyway. Liquibase is also more flexible than Flyway.”
Ming Li
CEO
Computer Software Company
No items found.
No items found.
Database DevOps best practices to your inbox
