sarama

I have found clients based on librdkafka [1] or sarama [2] to be pretty robust and capable. For SSL, librdkafka relies heavily on OpenSSL which can cause a few headaches IME. But the rest is straightforward. [1] https://github.com/edenhill/librdkafka [2] https://github.com/Shopify/sarama

I am currently a Master's student at one of the top Canadian universities. Before pursuing this, I worked for 4 years as a Software Engineer. I am finishing the program and interviewing aggressively in Toronto these days. Most of the interviews would pair me with another engineer (sometimes a fresh undergrad) for an hour long live coding session. Although I have been practicing and I am generally good at algorithms, I tend not to perform well in these sessions as I feel too much pressure. On the contrary, I have almost always previously performed really well in take-home assignments and landed the opportunities that I had sought earlier. That includes all my previous companies including Shopify. I personally feel that live coding sessions are an unfair way to evaluate candidates. For example, I have contributed to open source before such

You're absolutely right; I've added [2015] to the title. For context: the company where I work is putting Kafka into production soon and we came across this post while trying to build an intuition for the tradeoffs of Kafka as a system. I thought I'd post it on HN to try to generate some discourse. It's good to hear that things have changed so much for the positive, though since we're using Go, the Shopify client [0] has been usable for a while. [0]: https://github.com/Shopify/sarama

We're using Kafka at Shopify and we're pretty satisfied with it. We wrote a client library for Go: https://github.com/Shopify/sarama