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.
Read full review
InfluxDB is very good at storing monitoring metrics (e.g. performance data). InfluxDB is not the right choice if you need to store other data types (like plain text, data relations etc.).
Read full review 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 Read full review Perfect handling telemetry data. Low latency, near real time. SQL-like language makes it easier to query. Read full review Cons deployment. Not as easy configuration isn't as straight forward, especially with the documentation Garbage collection could be improved upon Read full review GUI based administrator console Read full review Likelihood to Renew
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
, then it does change drill into being something more valuable than prestoDB
Read full review
InfluxDB is a near perfect product for time series database engines. The relatively small list of cons are heavily outweighed by it's ability to just work and be a very flexible and powerful database engine. The community and support provided by the corporation are the only areas I have little experience.
Read full review Support Rating
We have worked with the InfluxDB support team a few times so far and it has been positive. Issues submitted are worked on promptly and we have good feedback.
Read full review Alternatives Considered
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
Read full review
To be honest, I didn't look at alternatives since InfluxDB performs very well if you can oversee the lack of security and HA features. But for all challenges, there is an easy solution which brings you forward (e.g. read load balancing can be achieved by using a common HTTPS load balancer).
Read full review Return on Investment 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). Read full review Provided us a time series DB. With the SQL-like language, it is very easy to learn. Empowered us to keep track of our events. Read full review ScreenShots