Apache Drill vs Flyway: What are the differences?
Developers describe Apache Drill as "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. On the other hand, Flyway is detailed 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.
Apache Drill and Flyway can be primarily classified 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, Flyway provides the following key features:
- 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
"NoSQL and Hadoop" is the top reason why over 2 developers like Apache Drill, while over 6 developers mention "Superb tool, easy to configure and use" as the leading cause for choosing Flyway.
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.
What is Apache Drill?
What is Flyway?
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?
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.