Currently, we use
http://httpd.apache.org/docs/2.2/mod/mod_proxy_balancer.html
However, we are experimenting with
http://synapse.apache.org/ - first using a static configuration of RESTful and SOAP endpoints with a goal to use dynamic registration/de-registration, so we are more elastic. Our working assumption, which our experiments will seek to validate: synapse is a better framework to build data driven routing patterns to support deployment user stories like scoped environments and A/B comparison. This is all http in and out, so not an ESB.
BillK
-----Original Message-----
From: glassfish_at_javadesktop.org [mailto:glassfish_at_javadesktop.org]
Sent: Wednesday, September 23, 2009 11:57 PM
To: users_at_glassfish.dev.java.net
Subject: Re: choice of load balancer
Hi Mete,
It is mostly dependent on what user is comfortable with. We will suggest using GlassFish load-balancer plugin with Sun Java System Web Server, Apache or IIS. GlassFish load-balancer plugin is supported by Sun. For configuring load-balancer plugin, you can refer to blog :
http://blogs.sun.com/kshitiz/entry/one_stop_for_glassfish_load
Apache mod_jk also works well with GlassFish. Please refer to blog :
http://blogs.sun.com/dadelhardt/entry/loadbalancing_with_mod_jk_and_glassfish
Thanks,
Kshitiz
[Message sent by forum member 'kshitiz_saxena' (Kshitiz.Saxena_at_sun.com)]
http://forums.java.net/jive/thread.jspa?messageID=365463
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
For additional commands, e-mail: users-help_at_glassfish.dev.java.net