Liquibase vs Postico: What are the differences?
What is 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.
What is 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.
Liquibase and Postico 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, Postico provides the following key features:
- Peek inside your database. Then edit as needed.
- Design a database with a sound structure.
- Query, Enquire, Investigate.
"Great database tool" is the primary reason why developers consider Liquibase over the competitors, whereas "Very clean, respectable interface" was stated as the key factor in picking Postico.
Liquibase is an open source tool with 1.78K GitHub stars and 1.09K GitHub forks. Here's a link to Liquibase's open source repository on GitHub.
Orbitz, Viadeo, and Virgin Pulse are some of the popular companies that use Liquibase, whereas Postico is used by JustWatch, Montemedia, and Livestorm. Liquibase has a broader approval, being mentioned in 15 company stacks & 12 developers stacks; compared to Postico, which is listed in 8 company stacks and 8 developer stacks.
What is Liquibase?
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.