Liquibase vs Flyway: What are the differences?
Liquibase and Flyway are both Java-based database tools for refactoring and versioning; Flyway uses SQL to define database changes, while Liquibase can also use XML, YAML, or JSON.
What is Flyway?
What is Liquibase?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Liquibase vs Flyway?
- Flyway is typically used by developers who want complete control over their SQL; it’s designed to do that one thing, and to do it well.
- On the other hand Liquibase is often cited as being a great database tool that supports many databases.
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Flyway vs Liquibase #Migration #Backwards-compatible
We were looking for a tool to help us integrating the migration scripts as part of our Deployment. At first sight both tools look very alike, are well integrated with Spring, have a fairly frequent development activity and short release cycles.
Liquibase puts a lot of emphasis on independence with the DB, allowing you to create the scripts on formats like JSON and YML, abstracting away from SQL, which it's also supported. Since we only work with one DB type across services we wouldn't take much advantage of this feature.
Flyway on the other hand has the advantage on being actively working on the integration with PostgreSQL 11, for it's upcoming version 6. Provides a more extensive set of properties that allow us to define what's allowed on what's not on each different environment.
Instead of looking for a tool that will allow us to rollback our DB changes automatically, we decided to implement backwards-compatible DB changes, for example adding a new column instead of renaming an existing one, postponing the deletion of the deprecated column until the release has been successfully installed.
it works with complex SQL script and it is very high customizable.