Re: [jetty-users] Fast request forwarding

[Martin Hewitt <martin.hewitt@xxxxxxxxx>]

Hi Mike,

Thanks for the HAProxy link. The main reason I'm moving towards Jetty
is that the failover component I'm writing deals with much more than
just directing traffic, so the proxying is more of an add-on to an
existing failover service than the primary purpose of it.

I'll look at subclassing the ProxyServlet, thanks.

Martin

On 4 April 2011 12:28, Mike Pilone <MPilone@xxxxxxx> wrote:
> While I love Jetty, it sounds like you might be better off using something like HAProxy which will do all the backend server polling and fail-over work for you. Check it out here: http://haproxy.1wt.eu/
>
> That being said, I'm using a home built HTTP reverse proxy running on Jetty as a simple front end router in environments where we don't have a real load balancer and as far as I have measured the performance impact is extremely minimal (a few MS per request). My proxy uses Apache's http client so you might be able to get even better performance with Jetty's own client library and continuations. You might be able to subclass Jetty's ProxyServlet to dynamically determine the proxy URL based on your backend tracking.
>
> -mike
>
>  | Mike Pilone | Software Architect, Distribution | mpilone@xxxxxxx | o: 202-513-2679  m: 703-969-7493
>
>
> -----Original Message-----
> From: jetty-users-bounces@xxxxxxxxxxx [mailto:jetty-users-bounces@xxxxxxxxxxx] On Behalf Of Martin Hewitt
> Sent: Monday, April 04, 2011 5:55 AM
> To: JETTY user mailing list
> Subject: [jetty-users] Fast request forwarding
>
> Hi all,
>
> I'm looking at creating a failover controller component that will
> monitor a cluster of servers and, should they fail, redirect traffic
> to a different cluster.
>
> The failover response needs to be swift, which is why this is
> happening in the application level instead of somewhere like DNS.
>
> I'm looking at Jetty because we use it widely in our other software
> packages, and it'd be nice to keep a consistent collection of
> libraries.
>
> My current thinking is that the component will know which cluster is
> "active" and will simply forward on requests to that component, so my
> question is: what's the fastest way of passing on these requests? A
> simple ProxyServlet or is there a speedier way?
>
> Thanks,
>
> Martin
> _______________________________________________
> jetty-users mailing list
> jetty-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/jetty-users
>
> _______________________________________________
> jetty-users mailing list
> jetty-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/jetty-users
>