----- Original Message ----- From: "Dave Watts" <[EMAIL PROTECTED]> To: "CF-Server" <[email protected]> Sent: Sunday, April 23, 2006 1:52 PM Subject: RE: Separate ColdFusion and IIS servers
>> Interesting. I would have for sure put it at being slower - >> unless there is a cracking network in place. > > Well, that's what I thought too, but I guess the cost of running both > processes on the same server can outweight the cost of having the > servers > communicate across a network. You run into the same issues with running > separate database and web application servers, and we recognize the > advantage of doing that. > >> This setup however, can and in most cases produces a single >> point of failure with a single code repository. > > How is there any more a single point of failure than there would be if > you > put both servers on the same machine? Actually, you have what I'd call mulitple single points of failure, which will make this configuration more vulnerable to machine downtime vs. running on a single machine. If either the web or the CF server goes down, is unresponsive, or is being rebooted for maintenance, then you've lost the web site. Similar to the common advice to run separate database and CF/web servers. Unless you're clustering both systems or have other ways to achieve redundancy, then it's virtually unavoidable that this will lead to increased downtime. It's probably still a good idea for a number of other reasons, but overall reliability really isn't one of them. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:10:5927 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/10 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:10 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.10 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
