Flyway vs Massive: What are the differences?
Developers describe Flyway as "Database Migrations Made Easy". Easy to setup, simple to master. Flyway lets you regain control of your database migrations with pleasure and plain sql. Solves only one problem and solves it well. Flyway migrates your database, so you don't have to worry about it anymore. On the other hand, Massive is detailed as "A Postgres-Centric Data Access Tool". Massive's goal is to help you get data from your database. This is not an ORM, it's a bit more than a query tool - our goal is to do just enough, then get out of your way. Massive embraces SQL completely, and helps you out when you don't feel like writing another mundane select * from statement.
Flyway and Massive can be categorized as "Database" tools.
Flyway and Massive are both open source tools. It seems that Flyway with 4.2K GitHub stars and 915 forks on GitHub has more adoption than Massive with 2.55K GitHub stars and 194 GitHub forks.
What is Flyway?
What is Massive?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Massive?
What are the cons of using Massive?
What companies use Massive?
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.