I don't agree with part 1 even, with the advent of vmware/xen/virtualbox
there is no reason to cram a bunch of stuff on a single server. It makes
your infrastructure way less upgradable, reliable, and testable.
a) The rewriting in resin is pretty good, its all regex, just like any
other rewrite. You may have to learn some new stuff, but that kind of how
IT works :)
b) You can do this with resin vhosts as well, either ip based or ipless.
c) You can also do this with resin :) http://quercus.caucho.com/
d) Same thing, but if you use a virtualization product its a no brainer to
clone production instances for QA on the same hardware.
I find resin by itself to be faster and easier to manage. The less software
you run the easier and safer your site will be. Running apache introduces
more code that you need to patch and manage, and apache is not the safest or
fastest webserver on the market.
Just some food for thought :)
On Tue, Mar 10, 2009 at 1:41 PM, Jan Kriesten <kries...@mail.footprint.de>wrote:
> > Why use Apache at all?
> there's more than one reason. Serving different sites/services on the same
> server, not all can be served by resin for various reasons:
> a) Rewriting Service:
> mod_rewrite has no real pendent
> b) Different Servlet-Containers on port 80:
> There are a couple of services which just wont run under resin (my favorite
> TeamCity which runs on a Tomcat instance because of that).
> c) PHP
> Not everything's running with resin and there are some projects out there
> just need the Apache-PHP plugin
> d) Different resin-instances on port 80:
> I don't want my TestEnvironment interfere with Live Services when a restart
> the container is necessary.
> Apache is a nice and powerful software to combine these different aspects
> Best regards, --- Jan.
> resin-interest mailing list
resin-interest mailing list