Apache Drill vs Liquibase: What are the differences?
What is Apache Drill? Schema-Free SQL Query Engine for Hadoop and NoSQL. Apache Drill is a distributed MPP query layer that supports SQL and alternative query languages against NoSQL and Hadoop data storage systems. It was inspired in part by Google's Dremel.
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.
Apache Drill and Liquibase can be categorized as "Database" tools.
Some of the features offered by Apache Drill are:
- Low-latency SQL queries
- Dynamic queries on self-describing data in files (such as JSON, Parquet, text) and MapR-DB/HBase tables, without requiring metadata definitions in the Hive metastore.
- ANSI SQL
On the other hand, Liquibase provides the following key features:
- Supports code branching and merging
- Supports multiple developers
- Supports multiple database types
"NoSQL and Hadoop" is the primary reason why developers consider Apache Drill over the competitors, whereas "Great database tool" was stated as the key factor in picking Liquibase.
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.
What is Apache Drill?
What is Liquibase?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Apache Drill?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Apache Drill?
What tools integrate with Liquibase?
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.