Thanks, I have to still trying to convince some people that Tomcat can
perform without a lot more of resources than Apache Http Server does.
Johann
--
View this message in context:
http://www.nabble.com/Tomcat-Farm-Recommendation-tf4025344.html#a11463888
Sent from the Tomcat - User mailing list
there is no right or wrong solution, but entertain this scenario
1. few very large machines (or)
2. many very inexpensive machines
in the case of one machine breaking, using 1) will have a larger impact
on your performance than 2)
however, in the case of 2) you may have more failures.
take go
Thanks for your reply, I know that there are a lot of things to consider to
give this kind of answer but my question was more about what do you have
that has worked for a corporate site, we're going to have mostly stateless
RPC Servlets for a Client Side RIA (GWT) and our scope is millions of user
First things first, I do not have an answer. As for the approach of multiple
machines it does allow for better fault tolerance. But is also has the
disadvantage of multiple machines to manage. And I am sure the list has lots
of other pros and cons. As for the machine brand selection is another a
