Harsh,

We looked at some of the other client libraries for .NET and opted to use the 
Kafka-Rest proxy.

There are challenges with using it, since it is stateful.

You can only run and connect to a single instance at a time.

By that I mean, if you have 3 consumers in a group you still must connect to 
the same instance of the proxy.

We have made our systems idempotent to account for a failure and re-parsing of 
the messages.

Besides that, it works fine.

Heath

-----Original Message-----
From: Fastmail [mailto:harsh...@fastmail.fm] 
Sent: Saturday, April 09, 2016 7:55 PM
To: users@kafka.apache.org; users@kafka.apache.org
Subject: Re: .Net Kafka Clients

Hi Dave,           We have our users running this client 
https://github.com/Microsoft/Kafkanet. 

Thanks,Harsha
    _____________________________
From: Tauzell, Dave <dave.tauz...@surescripts.com>
Sent: Friday, April 8, 2016 11:39 AM
Subject: .Net Kafka Clients
To:  <users@kafka.apache.org>


We are about to embark on using Kafka and will be starting out with a .Net 
based (C#) application.   I see a couple of active .Net Kafka libraries as well 
as the Confluent Kafka Rest Proxy.   We can write the readers in Java or some 
other language, so our .Net application only needs to write to Kafka.

Does anybody have any real-world experience with using Kafka from .Net?

-Dave

Dave Tauzell | Senior Software Engineer | Surescripts
O: 651.855.3042 | www.surescripts.com<http://www.surescripts.com/> |   
dave.tauz...@surescripts.com<mailto:dave.tauz...@surescripts.com>
Connect with us: Twitter<https://twitter.com/Surescripts> I 
LinkedIn<https://www.linkedin.com/company/surescripts-llc> I 
Facebook<https://www.facebook.com/Surescripts> I 
YouTube<http://www.youtube.com/SurescriptsTV>


This e-mail and any files transmitted with it are confidential, may contain 
sensitive information, and are intended solely for the use of the individual or 
entity to whom they are addressed. If you have received this e-mail in error, 
please notify the sender by reply e-mail immediately and destroy all copies of 
the e-mail and any attachments.



  

Reply via email to