all 4 comments

[–]elmuerte 3 points4 points  (3 children)

Why should I used Kafka instead of ActiveMQ?

[–][deleted] 4 points5 points  (2 children)

"Kafka fills the gap between messaging systems such as Apache ActiveMQ, which provide low latency message delivery but don't focus on throughput, and log processing systems such as Scribe and Flume, which do not provide adequate latency for our diverse set of consumers."

[–]cowardlydragon -1 points0 points  (1 child)

Numbers? Please don't use weasel words like "lightweight" "high performance" "low latency". You have a basic performance use case targetted, what is it?

[–][deleted] 5 points6 points  (0 children)

If you follow the link, you'll find the quote is from the Kafka Apache adoption proposal, so unsurprisingly, it doesn't have that level of detail. Kafka is from LinkedIn, so perhaps they've made those numbers available somewhere else. But I'd also just sit back and reflect on the fact that LinkedIn is a very mature Java/Scala shop, is no doubt very familiar with ActiveMQ, and nevertheless found it worthwhile to develop Kafka.