|
That's
why I said two of *everything* :)
Acceptable downtime, IMHO depends on what will be lost if your app is
offline, how quickly you think you can get it back up. Weigh that against the
cost of having multiple redundant everything.
It is
not a question of if your hardware will fail it is a question of when.
Everything fails in time so you need to come up with some best guess as to what
your mean time between failures is likely to be. Plus if you have two of
everything then you can take bits down for servicing, patching, etc without
effecting availability.
B
Good
points Barry... but lets say your DB server dies... make it the RAID card or
something on board so it's really gone... do you think that's going to be up
in an hour? (I'm actually wondering what is acceptable downtime... but I
think if it was something like this it'd be longer than an
hour?)
(By
the way, we have the same setups as you've described)
-
James
It
very much depends on how mission critical your app is. If you are running an
e-commerce site and an hour of downtime is going to cost you $70,000 then
yes having two of everything makes sense. If you are going to lose $500 then
probably not.
On
a side note you don't necessarily need Enterprise or need to 'cluster' the
boxes. You could have x number of app servers running Standard with
some kind of load balancer out the front. The LB would split the incoming
traffic amongst the available boxes. If a single box fails then it gets
taken out of the loop and traffic is directed to the remaining boxes.
However, in this case tho you would lose any session info on the box that
goes down.
On
the other point. You could have a front end web server serving static
content (images, static html pages, etc) and only forwarding .cfm requests
back to the app server. Having said that we combine the Web & CF servers
on the same box and have a separate box running the database
server.
Barry
But what about if one of those boxes fails
? This leads me to think you need 2 CF boxes running enterprise with
cluster cats. but then if you do that you might as well have 2 of
everything ? (sounds more like an Ark than a server farm!)
And assuming your application is entirely
written in CF, whats the point of having a separate web server ? all the
requests will be forwarded on to CF processing anyways ?
Pat
Maybe there is a bit of latency to deal with when the SQL server
is on another machine, but the benefits outweigh those milliseconds
lost.
The 4 main benefits you gain from keeping it all separate is
1. security
2. stability
3. scalability
4. upgradeability
But to answer your question, nope I don't know of any white
papers, but any decent networking guy should know this, keep it all
separate
- Web Servers
- SQL Servers
- Application Servers
- Mail Servers
I think if you have an architecture as
following
Box1 ColdFusion
Box2 SQL Server
Box3 Web Server
and a 100MBps network you won't notice any
latency and possibly gain speed.
Taco
Fleur
Tell me and I will
forget
Show me and I will remember
Teach me and I will
learn
Anyone
know about an official paper re best practice server architecture
configuration of CFMX, db servers, etc.
Basically
looking for something that sais the database server should reside on a
separate box to the CF app server. I'm arguing against someone who
insists network latency in accessing data has a bigger impact than the
sheer load oracle running on the same box as a couple of
instances of cfmx app servers.
Thanks
Scott. IMPORTANT NOTICE: This e-mail and any
attachment to it are intended only to be read or used by the named
addressee. It is confidential and may contain legally privileged
information. No confidentiality or privilege is waived or lost by any
mistaken transmission to you. The RTA is not responsible for any
unauthorised alterations to this e-mail or attachment to it. Views
expressed in this message are those of the individual sender, and are
not necessarily the views of the RTA. If you receive this e-mail in
error, please immediately delete it from your system and notify the
sender. You must not disclose, copy or use any part of this e-mail if
you are not the intended recipient.
---
You are currently
subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe
send a blank email to [EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney,
Australia
http://www.mxdu.com/ + 24-25 February, 2004
---
You are currently subscribed to cfaussie
as: [EMAIL PROTECTED]
To unsubscribe send a blank email to
[EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon
AsiaPac + Sydney, Australia
http://www.mxdu.com/ + 24-25 February, 2004
---
You are currently subscribed to cfaussie as:
[EMAIL PROTECTED]
To unsubscribe send a blank email to
[EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon
AsiaPac + Sydney, Australia
http://www.mxdu.com/ + 24-25 February, 2004
---
You are currently subscribed to cfaussie as:
[EMAIL PROTECTED]
To unsubscribe send a blank email to
[EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon
AsiaPac + Sydney, Australia
http://www.mxdu.com/ + 24-25 February, 2004
---
You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia
http://www.mxdu.com/ + 24-25 February, 2004
|
