Flyway vs Postico: What are the differences?
Flyway: 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; Postico: A modern PostgreSQL client for OS X. Postico provides an easy to use interface, making Postgres more accessible for newcomers and specialists alike. Postico will look familiar to anyone who has used a Mac before. Just connect to a database and begin working with tables and views. Start with the basics and learn about advanced features of PostgreSQL as you go along.
Flyway and Postico can be primarily classified as "Database" tools.
Some of the features offered by Flyway are:
- Supported databases: Oracle, SQL Server, SQL Azure, DB2, DB2 z/OS, MySQL, MariaDB, Google Cloud SQL, PostgreSQL, Redshift, Vertica, H2, Hsql, Derby, SQLite
- Supported build tools: Maven, Gradle, Ant and SBT
- Works on: Windows, Mac OSX, Linux, Java and Android
On the other hand, Postico provides the following key features:
- Peek inside your database. Then edit as needed.
- Design a database with a sound structure.
- Query, Enquire, Investigate.
"Superb tool, easy to configure and use" is the top reason why over 6 developers like Flyway, while over 3 developers mention "Very clean, respectable interface" as the leading cause for choosing Postico.
Flyway is an open source tool with 4.2K GitHub stars and 915 GitHub forks. Here's a link to Flyway's open source repository on GitHub.
According to the StackShare community, Flyway has a broader approval, being mentioned in 15 company stacks & 19 developers stacks; compared to Postico, which is listed in 8 company stacks and 8 developer stacks.
What is Flyway?
What is Postico?
Need advice about which tool to choose?Ask the StackShare community!
What are the cons of using Postico?
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.