Kafka's scalability is also demonstrated by its ability to handle spike of the events. Also since the flume topology needs to be changed, it requires some down time. It is not really a scalable solution when you have huge number of consumers. In contrast, adding more consumers to Flume means changing the topology of Flume pipeline design, replicating the channel to deliver the messages to a new sink. It is the consumers' responsibility to do the tracking through offset. It simply keeps all messages in the topic within a configurable period. That's because Kafka does not track which messages in the topic have been consumed by consumers. One of the key benefits of Kafka is that it is very easy to add large number of consumers without affecting performance and without down time. Compared to Flume, Kafka wins on the its superb scalability and messsage durablity.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |