requests.... handling all that I/O.....
Load on the disks will be astronomically high. All that DB access and page
access for the web-server...
Security.
If the web-server is dual homed, you can put the database on a private,
non-routable IP address so you dont have your datasource hanging out on the
Internet for everyone to see....
The biggest site I've built had 4 CF web-servers load balanced, 1
application server, 1 file server, 2 DB servers being clustered in an
active/passive setup.
The file server had 4 100Mb network cards set up to load balance the page
reguests from the web-servers.
The application server has 4 100Mb network cards set up as two teams and
provides the heavy duty processing for non-user requested tasks.
The web-servers and DB servers all have 100Mb network cards in place.
That little set up serves over 1000 simultaneous sessions (uses client
variables) 24/7. Fast, scalable architecture that just cannot be beaten.
It's been up and running for 3 years and our highest uptime on that set up
was 452 days without a reboot.
This reliability was due to the fact that the servers were sized accordingly
due to expected demands and the tasks were thought about in depth and split
out so that no one server would be overloaded.
IMHO, multiple boxes is the way to go.
Paul
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
