[LRUG] Intelligent load balancing

David Salgado david at digitalronin.com
Tue Mar 4 08:04:21 PST 2014


Hi Ed

We make heavy use of HAProxy, although not for that exact use case.

HAProxy can be configure to listen on a separate socket which you can use
to interrogate/control it. So, I think you could write a script to monitor
whatever conditions you like, and send commands to HAProxy to tell it how
to route traffic, on the fly.

The socket protocol looks really simple;

http://cbonte.github.io/haproxy-dconv/configuration-1.5.html#9.2

Aside from that, HAProxy is extremely fast, very robust and pretty simple
to configure. I'd definitely recommend it.

Hope this helps

David


On 4 March 2014 14:29, Ed James (Alt) <ed.james.spam at gmail.com> wrote:

>  Hi all
>
> We make heavy use of AWS services and we are finding that ELB is not quite
> meeting our needs. ELB allows some level of control over traffic, but it's
> dumb in the sense that it's done purely on load. You cannot put any real
> logic into ELB. What we want is to direct a user's requests based on an
> application setting - this could be in the db, memcache, redis, whatever.
> The retrieval of the setting is another problem I think. It's the logic
> around that setting's value that I'm interested in.
>
> We are doing a large upgrade of our platform and we want to run both the
> new version and old version in production in parallel. We want to control
> which customers get to see the new version and slowly increase the number
> of customer who can. If there is a problem we can just send all traffic
> back to the old version in an instant. This could just as easily apply to
> large feature deployments.
>
> Does anyone have any experience with this kind of use-case?
>
> Thanks,
> Ed.
>
> _______________________________________________
> Chat mailing list
> Chat at lists.lrug.org
> http://lists.lrug.org/listinfo.cgi/chat-lrug.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lrug.org/pipermail/chat-lrug.org/attachments/20140304/ab24f81b/attachment-0003.html>


More information about the Chat mailing list