Recommendations to others considering Apache Flume:
Apache Flume might be a good fit when simple transformations on the data are only that's required while streaming from source to sink. It is also highly scalable but comes with at the price of being less reliable, and it is also easy to lose data if proper fault-tolerant strategies are not in place. If the data being streamed is highly sensitive and needs to be replicated to ensure fault tolerance and persistence, consider other streaming application configurations like Apache Kafka, Splunk, or Apache NiFi. These alternatives offer better control on the persistence of data with replay and resume from a previous section in the stream of data. They also support multiple consumers reading from the same stream of data independent of each other. This is particularly important and useful if your one or many of the nodes in your configuration go down in the middle of streaming activity. Review collected by and hosted on G2.com.
What problems is Apache Flume solving and how is that benefiting you?
Apache Flume can be used to stream logs generated from an online transaction processing application and sent to other consumer applications for analytical purposes. One of the benefits of using Flume is that it is highly scalable and the components can be plugged in as required. Review collected by and hosted on G2.com.