Do it if you need to(performance, security, etc), but don't make things more complicated if you don't need to.
Do it if you need to(performance, security, etc), but don't make things more complicated if you don't need to. It used to be the standard to front Tomcat with an Apache server, but recent versions of Tomcat can(and often times are) used as both the HTTP Server and the Servlet Container. Take a look at the Tomcat Connector FAQ for information on the subject.
Why should I integrate Apache with Tomcat? (or not) There are many reasons to integrate Tomcat with Apache. And there are reasons why it should not be done too.
Needless to say, everyone will disagree with the opinions here. With the performance of Tomcat 5 and 6, performance reasons become harder to justify.... Speed. Apache is faster at serving static content than Tomcat.
But unless you have a high traffic site, this point is useless. But in some scenarios, tomcat can be faster than Apache httpd. So benchmark YOUR site.
Tomcat can perform at httpd speeds when using the proper connector (APR with sendFile enabled). Speed should not be considered a factor when choosing between Apache httpd and Tomcat.
No, I don't have any performance issues (yet) as traffic is low. I thought it was standard practice to front Tomcat with Apache, so I was investigating. What about to reduce the war size (by removing some large images and Flash files)?
Is it worth setting up Apache for this reason? – George Feb 25 '10 at 1:31 what about security? Is there a argument for apache with security?
– Roo Jul 8 '11 at 7:24.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.