Skip to content

Commit 8d9604c

Browse files
tianzhoutianzhou
committed
docs: refine flyway vs liquibase
1 parent 31851a5 commit 8d9604c

File tree

2 files changed

+29
-22
lines changed

2 files changed

+29
-22
lines changed

‎content/blog/flyway-vs-liquibase.md‎

Lines changed: 29 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,18 @@
11
---
2-
title: 'Flyway (Redgate) vs. Liquibase: a side-by-side comparison for database schema migration'
2+
title: 'Flyway (Redgate) vs. Liquibase in 2025'
33
author: Cayden
4-
updated_at: 2024/03/04 19:21:21
4+
updated_at: 2025/01/06 19:21:21
55
feature_image: /content/blog/flyway-vs-liquibase/flyway-vs-liquibase-banner.webp
66
tags: Explanation
77
description: 'When looking for a database CI/CD and schema migration change tool, Flyway 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.'
88
---
99

10+
<HintBlock type="info">
11+
12+
As Flyway and Liquibase continue to iterate, we will update this post regularly.
13+
14+
</HintBlock>
15+
1016
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.
1117

1218
## What Flyway and Liquibase have in common
@@ -25,20 +31,20 @@ When looking for a database CI/CD and schema migration change tool, Flyway (Redg
2531

2632
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.
2733

28-
| | Flyway | Liquibase |
29-
| ------------------------------------------------------ | ------------------------------- | ------------------------------- |
30-
| [Product position](#product-position) | Schema Change & Version Control | Schema Change & Version Control |
31-
| [Developer interface](#developer-interface) | CLI | CLI |
32-
| [Supported databases](#supported-databases) | 22 Only SQL | 50 SQL & NoSQL DB |
33-
| [Programming language and installation](#installation) | Java + JVM | Java + JVM |
34-
| [Change execution](#change-execution) | SQL script + CLI | Changelog (XML) + CLI |
35-
| [Change order](#change-order) | Numbering of SQL files | Changelog (XML) |
36-
| [Database GitOps](#database-gitops-configuration) | ✅ | ✅ |
37-
| [SQL auto check](#sql-auto-check) | ✅ | ✅ |
38-
| [Change history](#change-history) | ✅ | ✅ |
39-
| [Sync schema](#sync-schema) | ✅ | ✅ |
40-
| [Rollback](#rollback) | ✅ | ✅ |
41-
| [Schema drift detection](#schema-drift-detection) | ✅ | ✅ |
34+
| | Flyway | Liquibase |
35+
| ------------------------------------------------------ | ------------------------------- | -------------------------------------- |
36+
| [Product position](#product-position) | Schema Change & Version Control | Schema Change & Version Control |
37+
| [Developer interface](#developer-interface) | CLI | CLI |
38+
| [Supported databases](#supported-databases) | 22 Only SQL | 50 SQL & NoSQL DB |
39+
| [Programming language and installation](#installation) | Java + JVM | Java + JVM |
40+
| [Change execution](#change-execution) | SQL script + CLI | Changelog (SQL, XML, JSON, YAML) + CLI |
41+
| [Change orchestration](#change-orchestration) | Numbering of SQL files | Changelog |
42+
| [Database GitOps](#database-gitops-configuration) | ✅ | ✅ |
43+
| [SQL auto check](#sql-auto-check) | ✅ | ✅ |
44+
| [Change history](#change-history) | ✅ | ✅ |
45+
| [Sync schema](#sync-schema) | ✅ | ✅ |
46+
| [Rollback](#rollback) | ✅ | ✅ |
47+
| [Schema drift detection](#schema-drift-detection) | ✅ | ✅ |
4248

4349
### Product position
4450

@@ -76,13 +82,15 @@ While both Flyway and Liquibase are tools for database CI/CD, there are some key
7682
![liquibase-changelog](/content/blog/flyway-vs-liquibase/liquibase-changelog.webp)
7783
![liquibase-update](/content/blog/flyway-vs-liquibase/liquibase-update.webp)
7884

79-
### Change order
85+
### Change orchestration
8086

8187
- **Flyway**: Number the SQL files in the order you want them to be executed.
8288
![liquibase-change-order](/content/blog/flyway-vs-liquibase/flyway-change-order.webp)
8389
- **Liquibase**: Specify the order of changes in the changelog file.
8490
![liquibase-change-order](/content/blog/flyway-vs-liquibase/liquibase-change-order.webp)
8591

92+
Liquibase is more flexible as it can specify arbitrary orders. Also Liquibase provides a [flow file](https://docs.liquibase.com/liquibase-pro/flow/home.html) to orchestrate complex steps.
93+
8694
### Database GitOps configuration
8795

8896
- **Flyway**: Configure with VCS CI/CD workflow manually.
@@ -150,13 +158,12 @@ SQL auto check helps developers write less buggy SQL and save DBAs manual review
150158

151159
## Summary
152160

153-
Flyway and Liquibase are the two well-established tools for database CI/CD. They are similar in many ways, both are Java based, provide and only provide Java SDK and CLI, without GUI and API, adopt [migration-based](/blog/database-version-control-state-based-vs-migration-based/#migration-based-version-control-imperative) schema migration, and
154-
use the same open-source monetization strategy.
161+
Both Flyway and Liquibase are Java-based, offering with SDKs and CLI support, and follow a [migration-based](/blog/database-version-control-state-based-vs-migration-based/#migration-based-version-control-imperative) approach to schema changes.
162+
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.
155163

156-
The most significant difference is Liquibase has an additional [Changelog concept](https://docs.liquibase.com/concepts/changelogs/home.html) to allow user to specify explicit migration ordering, preconditions, labels and context,
157-
while Flyway relies on the [file naming](https://flywaydb.org/documentation/concepts/migrations#naming-1) to determine the order.
164+
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.
158165

159-
Both tools provide a git-like experience for database migrations. On the other hand, if you are looking for a GitHub/GitLab experience with a nice GUI and team collaboration features, please check out our own Bytebase and continue reading the side-by-side comparison with each of them:
166+
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:
160167

161168
- [Bytebase vs. Liquibase](/blog/bytebase-vs-liquibase/)
162169
- [Bytebase vs. Flyway](/blog/bytebase-vs-flyway/)

‎public/content/blog/flyway-vs-liquibase/star-history-flyway-vs-liquibase.webp‎

-53.2 KB
Loading

0 commit comments

Comments
 (0)