On 05/08/2009 6:41:37 PM, "Brent McArthur" <[email protected]> wrote:
Hi There,
What is everyone's opinion on whether or not you should an apache web server
sitting in front of tomcat magnolia in a production environment? Are there any
performance benefits?
I'm just curious.
A large proportion of my IT experience has been in developing custom java web
applications. As a default architecture, we pretty much always went with an
apache web server, tomcat app server approach so that apache web server could
effectively serve up all static content while leaving the dynamic stuff to
tomcat. This is also good from a scalability perspective.
But with Magnolia, a large proportion of what I would normally consider
"static" is managed by the CMS through the DMS (images, style sheets, etc.).
This means, Apache will really be doing nothing but passing all requests
through to Tomcat (mod_jk).
The only reason we have used Apache front-end (as a reverse proxy) is to allow
us to not to have to start Tomcat on port 80 (requires root or some other APR
set up). There is port forwarding of course, but we used Apache. The other
part where we saw performance difference was in SSL and compression. For
larger responses Apache compression was more efficient than Tomcat (less CPU
load).
Rakesh
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
