I realise I'm coming late to this discussion, but I used to use Apache
in front of Tomcat and it was always just an irritation more than
anything else - just one more complicated configuration that didn't
really seem to be adding anything.
We used Apache for serving static content and to allow us to do
virtual servers etc. and it worked ok, but whenever we wanted to
change anything it was a pain to have to deal with co-ordinating
several different apps etc. The apache configuration always seemed
extremely arcane and full of potential conflicts and pitfalls.
Now we use Glassfish as both the application server and web server -
configuration is much simpler, and the performance seems much, much
better than the Apache + Tomcat setup, even for simple static content.
Setting up virtual servers etc. is very simple can can easily be
configured via the GUI. The entire application ("static" content and
all) can be bundled into a single file for deployment and we can
redeploy a new build of a magnolia app in seconds with a single command.
I would definitely recommend you have a look at this option - I
certainly wouldn't go back to the Apache + Tomcat option unless there
was a very specialised reason that meant I had to do it.
Josh
On 6 Aug 2009, at 22:50, Brent McArthur wrote:
Hi Ralf/David/Rakesh,
Thanks a lot for your replies. Everything you've said makes sense.
We will use an apache web server for the reasons you listed.
Cheers
Brent
On 07/08/2009, at 12:45 AM, "Rakesh Vidyadharan"
<[email protected]> wrote:
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]>
----------------------------------------------------------------
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
