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 Apache Flume is well suited when the use case is log data ingestion and aggregate only, for example for compliance of configuration management. It is not well suited where you need a general-purpose real-time data ingestion pipeline that can receive log data and other forms of data streams (eg IoT, messages).
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 Multiple sources of data (sources) and destinations (sinks) that allows you to move data form and to any relevant data storage It is very easy to setup and run Very open to personalization, you can create filters, enrichment, new sources and destinations 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 It is very specific for log data ingestion so it is pretty hard to use for anything else besides log data Data replication is not built in and needs to be added on top of Apache Flume (not a hard job to do though) 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
Flume , then it does change drill into being something more valuable than prestoDB
Read full review Support Rating Apache Flume is open-source so support is limited. Never the less, it has great documentation and best practices documents from their end-users so it is not hard to use, setup and configure.
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 Apache Flume is a very good solution when your project is not very complex at transformation and enrichment, and good if you have an external management suite like Cloudera, Hortonworks, etc. But it is not a real EAI or ETL like AB Initio or Attunity so you need to know exactly what you want. On the other hand being an opensource project give Apache a lot of room to personalize thanks to its plug-able architecture and has a very nice performance having a very low CPU and Memory footprint, a single server can do the job on many occasions, as opposed to the multi-server architecture of paid products.
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 Flume has simplified a lot many of our ingest procedures, easier to deploy and integrate than a classical EAI, reducing the time to market But opposed to EAIs if the project starts to grow in complexity Apache Flume project may not be as suitable Read full review ScreenShots