Kudu as a More Flexible and Available Kafka-Style Queue

Re:Kudu as a More Flexible and Available Kafka-Style Queue by lobster_johnson on Tuesday January 26, 2016 @11:37PM (#10978243)

Thanks, that's helpful. We picked ES for several reasons. We're not a Java shop, and the Hadoop ecosystem is heavily biased towards JVM languages.

Secondly, ES is easy to deploy and manage. Being on the JVM, it admittedly has a considerable RAM footprint, but at least it's just one daemon per node. With anything related to Hadoop, it seems you have this cascade of JVM processes that inevitably need management. And lots and lots of RAM.

Thirdly, as you point out it's easy to do real-time writes.

I do like the fact that Kudu is C++.

[ Parent | on HN ]

Re:Kudu as a More Flexible and Available Kafka-Style Queue by jdcryans on Wednesday January 27, 2016 @12:16AM (#10978370)

Well TBH you do get to pick which Hadoop-related components need to run, HDFS's Datanode itself is happy with just a bit of RAM. I do understand the concern though.

You're probably happy with what you have in prod but if you get some time to try out Kudu feel free to drop by our Slack channel for a chat! http://getkudu.io/community.html

[ Parent | on HN ]

Re:Kudu as a More Flexible and Available Kafka-Style Queue by lobster_johnson on Wednesday January 27, 2016 @11:13AM (#10980811)

Thanks — I will definitely be keeping an eye on the project.

[ Parent | on HN ]