Thanks Radek, thanks David.
On Sun, Dec 23, 2012 at 12:08 AM, Radek Gruchalski <
radek.gruchal...@portico.io> wrote:
> That is exactly why we've decided to stick with java. Also support for all
> consumer settings out of the box.
>
> Kind regards,
> Radek Gruchalski
>
> On 22 Dec 2012, at 19:17,
That is exactly why we've decided to stick with java. Also support for all
consumer settings out of the box.
Kind regards,
Radek Gruchalski
On 22 Dec 2012, at 19:17, David Arthur wrote:
> FWIW, message production is quite simpler than consumption. It does
> not require the same complex coordin
We use that fork of node-kafka without any issues. We have a 3 server cluster
setup. Single topic, 3 partitions. No issues. Franz-kafka is on our "to check"
list but no rush yet.
Kind regards,
Radek Gruchalski
On 22 Dec 2012, at 18:59, Apoorva Gaurav wrote:
> Thanks Radek,
> We also are think
FWIW, message production is quite simpler than consumption. It does
not require the same complex coordination as the consumers. Producers
only use ZooKeeper to locate available brokers
Sent from my phone
On Dec 22, 2012, at 1:00 PM, Apoorva Gaurav wrote:
> Thanks Radek,
> We also are thinking o
Thanks Radek,
We also are thinking of Java / Scala for Consumers, for Producers whether
franz-kafka is a good choice?
--
Thanks & Regards,
Apoorva
On Sat, Dec 22, 2012 at 9:38 PM, Radek Gruchalski <
radek.gruchal...@portico.io> wrote:
> We started using node-kafka before we learned franz-kafka
We started using node-kafka before we learned franz-kafka was available. In
node, franz-kafka would be my preferred choice now. But tbh, our consumers are
all java. node-kafka does not support consumer settings like autooffset.reset
and so on (or it is not obvious how to use those).
Afair franz
