Apache Drill vs PrestoDB
Rating: 8 out of 10
IncentivizedUse Cases and Deployment Scope
Apache Drill was being used initially to evaluate running queries on data stored in multiple data stores (hDFS, postgres, cassandra). We were testing it out, over the use of PrestoDB. But saw that Drill also supported HBASE and other engines. it was from that aspect, used Drill to query data across the multiple datasources, as more ec2 instances were created, since some of the data was also stored in s3.
Pros
- queries multiple data sources with ease.
- supports sql, so non technical users who know sql, can run query sets
- 3rd party tools, like tableau, zoom data and looker were able to connect with no issues
Cons
- deployment. Not as easy
- configuration isn't as straight forward, especially with the documentation
- Garbage collection could be improved upon
Likelihood to Recommend
if you're doing joins from hBASE, hdfs, cassandra and redis, then this works.
Using it as a be all end all does not suit it. This is not your straight forward magic software that works for all scenarios. One needs to determine the use case to see if Apache Drill fits the needs. 3/4 of the time, usually it does.
Using it as a be all end all does not suit it. This is not your straight forward magic software that works for all scenarios. One needs to determine the use case to see if Apache Drill fits the needs. 3/4 of the time, usually it does.