Liquibase vs MaxScale: What are the differences?
Liquibase: Source control for your database. Developers store database changes in text-based files on their local development machines and apply them to their local databases. Changelog files can be be arbitrarily nested for better management; MaxScale: *A database proxy that extends high security *. It is a database proxy that extends the high availability, scalability, and security of MariaDB Server while at the same time simplifying application development by decoupling it from underlying database infrastructure.
Liquibase and MaxScale can be categorized as "Database" tools.
Some of the features offered by Liquibase are:
- Supports code branching and merging
- Supports multiple developers
- Supports multiple database types
On the other hand, MaxScale provides the following key features:
- high availability, scalability, and security
- simplifying application development
- transparent load
Liquibase is an open source tool with 1.82K GitHub stars and 1.1K GitHub forks. Here's a link to Liquibase's open source repository on GitHub.
What is Liquibase?
What is MaxScale?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose MaxScale?
What are the cons of using MaxScale?
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.