David Boreham wrote:
I think you also need to factor in the labor cost to manage two
different servers. I know that in our production deployments we could
buy many many machines for the cost of the time we've spent trying to
make AJP work. Tomcat could be 10x slower than Apache and I'd still
use it to avoid the hassle.
Of course if you need load balancing across multiple Tomcats you either
need Apache or a dedicated load balancer appliance.
Also Apache 2.2 allows easy configurable authentication (or a single
resource/URL) against multiple authentication repositories, e.g.
multiple LDAPs. Last I investigated Tomcat did not.
I'd love to see a simple world of only needing Tomcat and no front-end
web server. For starters Tomcat should provide high-performance
load-balancing from one "front-end" Tomcat to multiple "backend" Tomcats
and easy authentication against multiple LDAPs. After that there are
other issues, e.g. security providers that provide Apache but not Tomcat
plug-ins, but these would seemingly impact far fewer folk. In fact, I'd
bet fairly few of us need the multi-LDAP stuff -- just giving good,
high-performance load balancing over Tomcats by a Tomcat would be huge.
--
Jess Holle
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
