As Flyway and Liquibase continue to iterate, we will update this post regularly.
When looking for a database CI/CD and schema migration change tool, Flyway (Redgate) and Liquibase are two common options. Understanding the differences between these two tools can help potential users choose the one that best meets their needs.
What Flyway and Liquibase have in common
- Java-based, providing Java SDK and CLI.
- Provide open-source community version and closed-source commercial version.
- Native SQL supported, however Liquibase requires XML changelog to define the changes.
- Database CI/CD with version control system #GitOps (see Database GitOps configuration).
- Auto SQL check (see Auto SQL check).
- Schema Synchronization (see Sync schema).
- Tiered pricing, offering both free and paid plan.
- Open source, both has long history.
What are the differences between Flyway and Liquibase?
While both Flyway and Liquibase are tools for database CI/CD, there are some key differences between the two. The following table summarizes the differences between Flyway and Liquibase.
| Flyway | Liquibase | |
|---|---|---|
| Product position | Schema Change & Version Control | Schema Change & Version Control |
| Developer interface | CLI | CLI |
| Supported databases | 22 Only SQL | 50 SQL & NoSQL DB |
| Programming language and installation | Java + JVM | Java + JVM |
| Change execution | SQL script + CLI | Changelog (SQL, XML, JSON, YAML) + CLI |
| Change orchestration | Numbering of SQL files | Changelog |
| Database GitOps | ✅ | ✅ |
| SQL auto check | ✅ | ✅ |
| Change history | ✅ | ✅ |
| Sync schema | ✅ | ✅ |
| Rollback | ✅ | ✅ |
| Schema drift detection | ✅ | ✅ |
Product position
-
Flyway: A database schema change and version control tool.
-
Liquibase: A database schema change and version control tool. It helps you track, manage, and automate changes to your database.
Developer interface
-
Flyway: A command-line tool. With JVM, it also provides Java API, Maven plugin and Gradle plugin. A simple graphical user interface (GUI) called Flyway Desktop is available for SQL Server, PostgreSQL and MySQL.
-
Liquibase: A command-line tool. A simple graphical user interface (GUI) called Liquibase Hub is available with the Pro Plan, but it has sunset in May 2023.
Supported databases
- Flyway: 22 SQL databases - MySQL, PostgreSQL, IBM DB2, MS SQL Server, Oracle, PostgreSQL, MySQL, Snowflake ...
- Liquibase: 50 SQL and NoSQL databases - IBM DB2, MS SQL Server, Oracle, PostgreSQL, MySQL, Snowflake, MongoDB, Clickhouse ...
Installation
-
Flyway: Java-based tool, so you need to install a Java Virtual Machine (JVM) before users can install Flyway.
-
Liquibase: Java-based tool, so you need to install a Java Virtual Machine (JVM) before users can install Liquibase.
Change execution
- Flyway: CLI or GitOps. Users write SQL files and then run command
flyway migrate.
- Liquibase: CLI or GitOps. Users specify the changes by defining a
changelogand then run a command.
Change orchestration
- Flyway: Number the SQL files in the order you want them to be executed.
- Liquibase: Specify the order of changes in the changelog file.
Liquibase is more flexible as it can specify arbitrary orders. Also Liquibase provides a flow file to orchestrate complex steps.
Database GitOps configuration
-
Flyway: Configure with VCS CI/CD workflow manually.
-
Liquibase: Configure with VCS CI/CD workflow manually.
SQL auto check
SQL auto check helps developers write less buggy SQL and save DBAs manual review efforts.
- Flyway: Code Analysis
- Liquibase: SQL Quality check
Supported plan
- Flyway: Only in Team Plan or above
- Liquibase: Only in Pro Plan and above
Number of rules
- Flyway: 10+ general rules or integrate a python app called SQLFluff to get more rules.
- Liquibase: 10 general rules
How to configure
-
Flyway: Predefined, users may set them active or not.
-
Liquibase: Predefined, users may set levels while calling.
How to trigger
-
Flyway: Run
flyway check -code ....command to produce a report.
-
Liquibase: Run
checkcommand or manually integrate this command in automation. Users may go to admin console to view logs.
Change history
- Flyway: Run
flyway infoto showflyway_schema_historytable.
- Liquibase: Simple Database Change Logs.
Sync schema
- Flyway: Via the flyway desktop, there is a way to generate a migration script to bring the target database schema in sync with the one you already created (usually dev).
- Liquibase: Support
diff-changelogto compare databases and to create a deployable changelog to sync.
Rollback
- Flyway: Write rollback scripts manually. Supported in Team version.
- Liquibase: Support
rollback-one-changesetorrollback.
Schema drift detection
- Flyway: Run
flyway check -drift ...to produce a report indicating difference between target database and the one created by the migrations applied by Flyway. - Liquibase: Run
liquibase diff --format=jsonto produce a report indicating difference between target database and source database.
Summary
Both Flyway and Liquibase are Java-based, offering with SDKs and CLI support, and follow a migration-based approach to schema changes. They also leverage the same open-source monetization strategy. While Flyway is generally considered more developer-friendly, Liquibase offers a broader set of advanced features.
The key difference is that Liquibase introduces the Changelog and Flow concepts, enabling users to specify explicit migration ordering, preconditions, labels, and contexts. In contrast, Flyway determines migration order based solely on file naming conventions.
Both tools offer a Git-like experience for database migrations. However, if you're seeking a GitHub/GitLab-style experience with a user-friendly GUI and team collaboration features, consider our own Bytebase. Continue reading for a side-by-side comparison with each tool:
the
