I would definately recommend two servers if for no other reason it is nice to be able
to upgrade one while the other is serving content. Also servers do crash.
We also use a staging server. Allaire actually recommended that we use a separate
database server for the staging server and export from one to the other. We did not do
this for a number of reasons. I am not sure what others are doing but would be
interested.
The staging server is used for input of all content and this is pretty CPU intensive.
The production servers cache most pages but the staging server does no caching of
files. We use an Arrowpoint switch to load balance and replicate the templates and
static files to the production servers in a publish/subscribe model.
Our servers are using a fiberChannel SAN although this is not necessary.
Lanny Udey
Hofstra University
>>> [EMAIL PROTECTED] Thursday, March 08, 2001 >>>
Hello,
I am starting a new spectra project at the moment and we are at the stage of
designing the server cluster architecture. In a previous architecture we
used 2 spectra servers and one db server with a raid unit. Does any one have
any recommendations on the best starting architecture for spectra. Also, one
of my team mates has recommended that we go with one spectra server and 1 db
server. My gut feeling tells me that we should go straight away to 2
webservers and deal with clustering issues of state management straight
away, anyone have any thoughts or comment on this?
Kind regards,
Frank
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/spectra_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
