Apache Drill vs. Google Cloud Datastore

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

I feel like Google Cloud Datastore is well suited when the data models are simple and the possible filtering and sorting operation are not complex. With more complex filtering, the amount of required indexes increase, and so does the costs.

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

• It is hosted in GCP, our primary cloud provider.
• It integrates with all the services we use in GCP.

Incentivized

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

Incentivized

• Part of the Google Cloud Platform walled garden.
• Pay for read/writes to the datastore, in addition to storage.
• Not many libraries exist.

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

I give Google Cloud a full score because it satisfies our needs so well. We host most of our infrastructure on Google Cloud and using Google Cloud Datastore helps us to solve our NoSQL storage problem. and Google Cloud Datastore is so scalable and elastic. It saves us lots of time to maintain and saves us money.

Incentivized

The simple implementation, together with the Google Cloud dashboard that allows data inspection, editing and querying, makes Google Cloud Datastore a comprehensive choice when it comes to NoSQL databases.

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

If deploying an application in Google Cloud Platform, using Google Cloud Datastore is a no brainer because of the simplicity of setup. Other options would require more setup and configuration, and do not come with the same level of guaranteed uptime as Google Cloud Datastore. In our case, we've been using Google Cloud Datastore for 4 years without any issues and have never had to think about it.

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 solves our NoSQL database problem.
• It it highly scalable and available to meets our needs.

Incentivized