Liquibase vs PostGIS: What are the differences?
Developers describe Liquibase as "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. On the other hand, PostGIS is detailed as "Open source spatial database". PostGIS is a spatial database extender for PostgreSQL object-relational database. It adds support for geographic objects allowing location queries to be run in SQL.
Liquibase and PostGIS 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, PostGIS provides the following key features:
- Processing and analytic functions for both vector and raster data for splicing, dicing, morphing, reclassifying, and collecting/unioning with the power of SQL
- raster map algebra for fine-grained raster processing
- Spatial reprojection SQL callable functions for both vector and raster data
"Great database tool" is the primary reason why developers consider Liquibase over the competitors, whereas "De facto GIS in SQL" was stated as the key factor in picking PostGIS.
Liquibase and PostGIS are both open source tools. It seems that Liquibase with 1.78K GitHub stars and 1.08K forks on GitHub has more adoption than PostGIS with 636 GitHub stars and 242 GitHub forks.
HotelTonight, Key Location, and DNT are some of the popular companies that use PostGIS, whereas Liquibase is used by Orbitz, Viadeo, and Virgin Pulse. PostGIS has a broader approval, being mentioned in 53 company stacks & 14 developers stacks; compared to Liquibase, which is listed in 15 company stacks and 12 developer stacks.
What is Liquibase?
What is PostGIS?
Need advice about which tool to choose?Ask the StackShare community!
What are the cons of using PostGIS?
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.
PostGIS makes it easy (and fast) to do geographic queries, such as nearest-neighbor and bounding box queries.
Backend for weather forecast data that Geoserver queries to build updated weather maps