Load Balancers
Is Terracotta a Load Balancer?
A question we get asked a lot is "is Terracotta a load balancer?" to which the answer is "No." Terracotta allows threads on multiple JVMs to interact with each other as if they were on the same JVM. But, it doesn't make multiple JVMs look to the outside world like one big JVM; and, it doesn't do load balancing.
That being said, we are often asked for help choosing a load balancer. Our biggest recommendation is that, if you are planning to deploy a web application on multiple application server machines with Terracotta-shared sessions, you choose a load balancer that supports sticky sessions—that is, one that routes requests with the same session id to the same physical server machine, if possible. This will help increase locality of reference by keeping the objects that are needed to process a request associated with a particular session as close to the location of that processing as possible. Your web cluster will be much faster if the data needed to service requests is already resident in memory in the application server that is servicing that request.
Load Balancer Resources
Below is a list of resources that may help you decide on a load balancing strategy. Please add more links to this page as you see fit.
http://www.onjava.com/pub/a/onjava/2001/09/26/load.html
http://www.networkworld.com/reviews/0614rev.html ,
http://tomcat.apache.org/tomcat-5.0-doc/balancer-howto.html (mod_jk, mod_proxy, mod_rewrite).
some solutions:
