-Re: Curator and queue recipe warning
Camille Fournier 2012-12-05, 03:36
That is generally accurate. ZooKeeper isn't written to be a distributed
queue in the high-throughput messaging kind of sense. If you need something
truly lightweight and simple to serve as a distributed queue for a few
messages, it might work. But for anything that could see significant
volume, there's better options out there.
ZooKeeper is used to implement several systems that will serve this need.
Depending on what you're looking for, you might check out:
Or many of the brokered messaging servers like ActiveMQ, etc.
On Tue, Dec 4, 2012 at 9:42 PM, Diego Oliveira <[EMAIL PROTECTED]> wrote:
> Hello folks,
> I got to the Curator wiki page to see something about the distributed
> queue recipe and got surprised with the big warning telling to not use
> zookeeper as a distributed queue controller, the reason page described some
> cases that I passed here... is this *TRUE*, if so, what option do we have.
> The message:
> *IMPORTANT* - We recommend that you do NOT use ZooKeeper for Queues. Please
> see Tech Note 4 <https://github.com/Netflix/curator/wiki/Tech-Note-4> for
> details. Links
> Diego de Oliveira
> System Architect
> [EMAIL PROTECTED]
> Never argue with a fool -- people might not be able to tell the difference