Tomcat 6 and Apache2 VS Tomcat 6 alone

Hi!

I posted this at "Nabble » Apache » Tomcat » Tomcat - User" =
aswell:=20
http://old.nabble.com/Tomcat-6-and-Apache2-VS-Tomcat-6-alone -td26493078.htm=
l

But I want some mixed input so I'll post it here aswell, so here goes.
Im pretty new to this but have 2 friends that help me out. Though one of my
friends tells me to use Apache2 infront of Tomcat and the other one tells m=
e
it's unnecessary.

I'll try to explain my situation:
I've started a virtual Ubuntu 8.04 Longterm server and my goal is to have
atleast one serious site (made in Grails) and beeing a search engine (think
youtube). So it's gonna be pretty much dynamic content and less static. But
I will also start some sites just for fun that probobly won't have that muc=
h
visitors but beeing abit more static content.
Im not saying my primary site will get much visitors but I want to build th=
e
environment as if it has.
Ps. I will probobly put a Varnish at the front sooner or later (for the
experience)

So what do you all think? Is the Apache2 infront of the Tomcat 6 a waste of
time or worth while?
I'd love to have as many inputs as possible!
--=20
View this message in context: http://old.nabble.com/Tomcat-6-and-Apache2-VS=
-Tomcat-6-alone-tp26494576p26494576.html
Sent from the Apache HTTP Server - Users mailing list archive at Nabble.com=
..


------------------------------------------------------------ ---------
The official User-To-User support forum of the Apache HTTP Server Project.
See for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org

Re: Tomcat 6 and Apache2 VS Tomcat 6 alone

--a8Wt8u1KmwUX3Y2C
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Unless you are Amazon or Google, any reason you might find for
choosing one vs. the other will probably have little to do with
performance. Recent Tomcat versions are not notably slow at serving
static content. And remember, with HTTPD/Tomcat, every request
and response has to make an extra trip through the local network stack
to cross the process boundary -- small wins may be overwhelmed by the
additional cost of frontending.

Some reasons I have for continuing to run HTTPD in front of Tomcat anyway:

o I learned HTTPD first and am still more comfortable with it
o I like HTTPD's configuration language better
o Lots and lots and LOTS of modules to make HTTPD do all sorts of
fancy things, if you want them.
o I absolutely *hate* the JKS certificate store. I very much prefer
setting up SSL for HTTPD than for Tomcat.
o That's the way I set it up originally and I don't want to mess with
it.

Others will have similar reasons for *not* running an HTTPD frontend.

One other reason I can think of: if you need HTTPD anyway for other
uses, you might want to keep all the network-related configuration
together.

--=20
Mark H. Wood, Lead System Programmer mwood@IUPUI.Edu
Friends don't let friends publish revisable-form documents.

--a8Wt8u1KmwUX3Y2C
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)

iEYEAREDAAYFAksNRmkACgkQs/NR4JuTKG+CZwCbBUMN0UhW0jCV5DUST9jA 5+em
PeQAniQ9FFJM/Ss0k2qZZ8xJMWJmtaCK
=Eo0s
-----END PGP SIGNATURE-----

--a8Wt8u1KmwUX3Y2C--