To circle back around this thread there is an available native .net client
https://cwiki.apache.org/confluence/display/KAFKA/Clients#Clients-.net now.
/***
Joe Stein
Founder, Principal Consultant
Big Data Open Source Security LLC
http://www.stealth.ly
T
The wire protocol has changed drastically since then.
I don't know of any C# clients (there are none on the client library page
nor have I heard of any being used in production but maybe there are some).
For clients that use DotNet I often suggest that they use some HTTP
producer/consumer
https:
Ok got some info myself.
I can have fault tolerance - I can start kafka-http-endpoint using
broker lists
I can have ack - start using --sync
But what is best practice in case if kafka-http-endpoint goes down?
Start multiple kafka-http-endpoint's and in client side just control
that kafka-htt
Thank you for response. I think HTTP is ok.
I have two more question in case of HTTP.
1. Can I have fault tolerance in case I have two or more brokers?
2. Can I ack that message is in queue?
Best regards, Margus (Margusja) Roo
+372 51 48 780
http://margus.roo.ee
http://ee.linkedin.com/in/margusro
Hi
I have kafka broker running (kafka_2.9.1-0.8.1.1)
All is working.
One project requires producer is written in CSharp
I am not dot net programmer but I managed to write simple producer code
using
https://github.com/kafka-dev/kafka/blob/master/clients/csharp/README.md
the code
...
using Sys
