Apache Flume vs. Starburst Enterprise

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).

Incentivized

If you run a SQL query, Starburst Presto can help you track efficiently the status of SQL query. It can also track how many resources have been allocated for execution and what is the optimal way to run the query without hindrance. It also provides good information on worker nodes and how parallel threads are running together.

Incentivized

• 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

Incentivized

• Query tracking.
• Resource allocation.
• Parallelizing query execution.

Incentivized

• 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)

Incentivized

• Pricing
• Platform can be made more intuitive.
• Sometimes the platform hangs while aborting the query.

Incentivized

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.

Incentivized

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.

Incentivized

Most of our systems were compatible with Starburst Presto. The dashboard which they provide was fairly intuitive and easy to use. The learning curve wasn't that much. Also, the parallel processing part was an additional feature that we didn't find in many competitive products. The pricing was a little higher but it was worth the trade-off.

Incentivized

• 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

Incentivized

• Neutral impact.
• ROI on saving time for query execution.
• Parallel processing saves time too.

Incentivized