Apache Drill vs. ArangoDB

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.

Incentivized

Use cases provided by default are good and can be improve better using Machine Learning and AI. AQL query language is very simple and efficient in use if anyone using SQL can quickly learn AQL Language.

Developers can easily map the database and can access various patterns like search, ranking.

JSON and semantic search is the latest and next-generation technology to implement to access and extract large datasets.

Incentivized

• 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

Incentivized

• AQL query language is big plus for ArangoDB
• It can be implemented cloud as well as on-prem
• Search Engine is a very good option for ArangoDB

Incentivized

• deployment. Not as easy
• configuration isn't as straight forward, especially with the documentation
• Garbage collection could be improved upon

Incentivized

• By providing the free services for few months will be help understand for beginners
• Enhancing features in dashboard and can make UI more user-friendly
• Should conduct more surveys and adv to improve scalability

Incentivized

if Presto comes up with more support (ie hbase, s3), then its strongly possible that we'll move from apache drill to prestoDB. However, Apache drill needs more configuration ease, especially when it comes to garbage collection tuning. If apache drill could support also sparkSQL and Flume, then it does change drill into being something more valuable than prestoDB

Incentivized

compared to presto, has more support than prestodb. Impala has limitations to what drill can support apache phoenix only supports for hbase. no support for cassandra. Apache drill was chosen, because of the multiple data stores that it supports htat the other 3 do not support. Presto does not support hbase as of yet. Impala does not support query to cassandra

Incentivized

It uses AQL query Language, which is different from other Databases. It has flexibility to integrate in cloud, on-prem anywhere

Incentivized

• Configuration has taken some serious time out.
• Garbage collection tuning. is a constant hassle. time and effort applied to it, vs dedicating resources elsewhere.
• w/ sql support, reduces the need of devs to generate the resultset for analysts, when they can run queries themselves (if they know sql).

Incentivized

• It is very powerful tool and should adv more to improve sales
• Should conduct more free trails and trainings
• Open source and runs everywhere

Incentivized