+1 everything Eric said. For macromedia.com (and now adobe.com) we had Apache on separate servers to ColdFusion because we handled a lot of static assets and Apache's pretty good at that and we also had a lot (thousands) of rewrite rules. We also had load balancers in front of each tier - round robin in front of Apache as I recall and sticky session in front of ColdFusion.
On Mon, Jun 13, 2011 at 9:29 AM, Eric Knipp <[email protected]> wrote: > There are very good reasons: > 1. Security - splitting server roles onto different physical or virtual > machines simplifies the task of locking down unnecessary services on each. > It also adds a layer of defense in depth: a web server exploit only exposes > the web server machine, and your application server is still safe. Intrusion > detection is important here, if a machine is compromised you need to know > about it. You can also add all kinds of inter-machine firewalls and > monitoring here. > 2. Management - patching, updating, backups are simplified as each machine > is performing an isolated task. > 3. Scalability - a load balancer can be slipped in between each > infrastructural tier. Provided you construct your apps with a stateless > architecture, scaling up is a relatively straightforward task of adding more > role-specific machines to the tier in question. > By the way none of this advice is ColdFusion or BlueDragon specific. > Hope that helps, > Eric > -- official tag/function reference: http://openbd.org/manual/ mailing list - http://groups.google.com/group/openbd?hl=en
