More specifically now,
I have noted two possible set ups:
1. Simpler round-robin algorithm to choose web server at the DNS level
and then have the web server load balance (with session awareness) to
servlet engines as it seems to be the case with Apache.
2. Have DNS itself be session aware (3-DNS from F5) and load balance to
HTTP server which would have only one instance of servlet engine.
I guess it comes down to: should one web server have many instances of
servlet engine on it? It seems that it is a good idea since it will
take much less for the HTTP server to relay request to servlet engines
and then send back a ready-made reply. It would seem a waste to have
just one servlet engine instance on one HTTP server. Is this assumption
correct?
It seems that the Apache way is better. In the second approach if DNS
is session aware then it would send request to a given web server and
the web server would again have to check the session ID to direct the
request to correct instance of the servlet engine?
Am I making sense here? Are there other setups? Can someone who has
done this share their knowledge?
dave.
--
David Mossakowski _||_ e-mail: [EMAIL PROTECTED]
Instinet Corporation __||||_|_||__||_ tel: 212.310.7275
Programmer __||||__||_|||__|||||_|__ fax: 212.583.7780
_||__|__"I don't sit idly by, I'm planning a big surprise"
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
