In some scenarios, usage of Flume is not the ideal choice. There are other options out there which can be employed to solve those use case and not Flume. Do not choose Flume when:
- You need more data processing as against transfer of data. They are more suited for other stream processing technologies.
- You need more batch data transfer scenarios (regular batch as against micro-batch).
- You need a more available setup with no data loss.
- You need a durable message with very high scalability requirements (there isn't a scientific quantitative figure for that though).
- You have a huge number of consumers as this has a very high impact on Flume’s scalability.
Even through Flume can be dynamically configured in many cases, it does incur downtime in certain configuration changes (topology changes).
