zookeeper-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From howard chen <howac...@gmail.com>
Subject Re: High availability backend services via zookeeper or TCP load balancer
Date Wed, 27 Feb 2013 09:43:59 GMT

On Wed, Feb 27, 2013 at 2:35 AM, Camille Fournier <camille@apache.org>wrote:

> You can definitely use ZK for this, as Jordan said. I would really question
> whether writing client-side code to do this vs using something that is
> really designed for writing load balancers (like haproxy) wouldn't be a
> better way to do it however. It doesn't sound like you are creating
> long-lived connections between these clients and services, and instead just
> want to send a request to an ip address that corresponds to the LB for that
> request. Your client-side code is probably going to be buggier and the
> setup/maintenance more complex than if you use a simple load balancer. If
> you're already using ZK for a lot of other things and it is really baked in
> to all your clients, maybe this is the easiest thing to do, but I wouldn't
> use ZK just for this purpose.
Yes, our connection is long lived (similar to web socket).

We don't have any ZK deployment as of today, but sound like the ZK's core
feature such as subscribe to notification is really interesting.

Of course, one of our concern is as ZK is quite low level for this kind of
usage, i.e. service discovery and fail over, so we would need to modify our
client to support this workflow (or by integrating framework like Neflix's

Are there any popular choice besides the Neflix's curator?

Thanks for all the input

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message