4 ms·

This needs a [2015]. Back then there wasn't a single usable client for .net. Since then the non-Java clients have massively improved. In particular https://git

by ah- 10y ago

This needs a [2015]. Back then there wasn't a single usable client for .net. Since then the non-Java clients have massively improved. In particular https://github.com/edenhill/librdkafka https://github.com/edenhill/librdkafka is fantastic. There's also https://github.com/dpkp/kafka-python/ https://github.com/dpkp/kafka-python/, with support for consumer groups and all the other modern features. The basic criticism of requiring a complex client is valid, however you cannot achieve the delivery guarantees that Kafka gives you without one. The alternative would be to have a local agent process like consul, but that wouldn't give you the throughput that Kafka gets. Disclaimer: I've built a C# client for Kafka based on librdkafa (https://github.com/ah-/rdkafka-dotnet https://github.com/ah-/rdkafka-dotnet), so I'm biased.

mscrivo 10y ago
FWIW, I've used your client and it's quite good. Thank you!
kornish 10y ago
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 https://github.com/Shopify/sarama
- sctb 10y ago
  We've removed the (2015) label now that there's an update at the top of the post.
KirinDave 10y ago
I would like to jump on the bandwagon saying thank you for your hard work on a good client for the C# world. But I do not see any issue with rehoming Kafka's coordination to Consul.
nostrebored 10y ago
RDKafka-Dotnet has been a lifesaver for me in creating a consumer in a new dotnet core application. Your hard work accelerated work on my project by weeks, and is much cleaner than the other dotnet kafka libraries available. Thank you so much!

by ah- 10y ago

mscrivo 10y ago

FWIW, I've used your client and it's quite good. Thank you!

kornish 10y ago

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 https://github.com/Shopify/sarama

sctb 10y ago
We've removed the (2015) label now that there's an update at the top of the post.

KirinDave 10y ago

I would like to jump on the bandwagon saying thank you for your hard work on a good client for the C# world. But I do not see any issue with rehoming Kafka's coordination to Consul.

nostrebored 10y ago

RDKafka-Dotnet has been a lifesaver for me in creating a consumer in a new dotnet core application. Your hard work accelerated work on my project by weeks, and is much cleaner than the other dotnet kafka libraries available. Thank you so much!