tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steffen Heil" <>
Subject AW: Search engine friendly URLs
Date Sun, 03 Oct 2004 15:18:19 GMT

> If you want to be able to scale your application, you need to be able to
move the static image handling out of tomcat to a separate web server. Using
Tomcat to handle both application chores and web serving chores will limit
the overall scalability of your system.

I strongly disagree.
Tomcat is nearly as fast as apache in serving images.
So, yes, you can save a little time using apache, BUT remeber that the
apache slows tomcat down. You need cpu-cycles for apache, for mod_jk and
additionally for tomcat. Those cycles for apache and mod_jk are not
nessesary, since tomcat can work standalone.
So the question comes down to decide wether the overhead of handling apache
and mod_jk for dynamic content is smaller then the difference of apache and
tomcat in serving images. I guess with current versions of tomcat the
overhead to apache and mod_jk is even bigger.
Hence, tomcat alone will be faster.
(Please also consider, that static content will mostly be taken from the
browsers cache, whereas dynamic content needs to be received from tomcat.
That means that the time won by using apache for static content needs to be
a magnitude higher than the overhead of mod_jk. That's simply not the case.)

Tomcat cannot do rewriting, that is correct, but it does not need to:
I use url such as:
where content is mapped to my servlet.
The parameter is simply the rest of the url.

You could do:
and parse the rest of the url to
  section = books
  subsection = architecture

Simply map to your servlet.


View raw message