I see , Is it a good Idea to use Node.js client? C# will produce messages to Node.js and Node.js will push it to the Kafka? Is there potential problem with such aproach? Thanks Oleg. On Wed, Apr 3, 2013 at 9:18 PM, Joel Koshy <[EMAIL PROTECTED]> wrote:
Maybe you could write a C# client. I don't think it would be super hard to write a basic one (that doesn't require zookeeper for example). C# has a lot of great features that would make it great for a solid kafka client. On Wed, Apr 3, 2013 at 3:58 PM, Oleg Ruchovets <[EMAIL PROTECTED]> wrote: Matthew Rathbone Foursquare | Software Engineer | Server Engineering Team [EMAIL PROTECTED] | @rathboma <http://twitter.com/rathboma> | 4sq<http://foursquare.com/rathboma>
You can certainly use different clients for producers and consumers. E.g., you could have a Python producer, a C producer, and a Scala consumer; or any combination thereof.
If you want your consumers to participate in a consumer group, you'll need to use the Java or Scala client (or a 3rd party client that supports consumer groups).
On 4/4/13 7:36 AM, Oleg Ruchovets wrote:
David Arthur 2013-04-04, 13:31
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation projects and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext