Hmmm ... i wish it was that simple. It isn't.

Anytime a new "neighbor" moves in on the server, or an existing neighbor
changes their codebase, you run the risk that it takes the server down or
strains its resources to the point where requests take 10 20 30 seconds for
awhile until the server crashes. That's true no matter how much you pay, or
how wonderfully helpful the webhost is. And it happens with a predicable
random certainty. It's not their fault ... they can't test every batch of
code that anyone uploads.

And yes, a good, expensive webhost will move such sites to a server on their
own. That's what you're paying extra for. But it takes them awhile to figure
out which site is tanking performance on the server, and move it. In my
experience, it often takes the better part of a day.

Meanwhile, some ... inexperienced person ...  is developing live on the
production server. The problem he's creating comes and goes. "Whoops, what
did i do?" he says to himself, as the 500 error comes up white on the
screen. Then after the server reboots and comes back online, he tries the
same request again, hoping for a more descriptive error screen. Beginners go
blank and freeze up when they hit an error, especially when they are
developing on a live server. And they'll have absolutely no clue what havoc
they are causing.

Who knows what happens after that? Maybe his mother calls him to dinner.
Maybe he sits there confused and makes it worse. Maybe his time at the
computer in the school library is up and he needs to get to his next class,
and he just leaves it.

*****

When you're employed, you don't lose your job on days when someone is
fiddling around like that on a server you've got a shared site on. But when
you're running your own small company, those are the days you lose clients,
or severly strain your reputation with them. Hosting is by far your most
vulnerable point - your achilles heel. I guess you guys working in an
enterprise environment, stress testing your apps for memory leaks and
bottlenecks on staging servers, live in a different world! :) nando



>-----Original Message-----
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
>Behalf Of Sean Corfield
>Sent: Sunday, November 06, 2005 7:41 PM
>To: [email protected]
>Subject: Re: [CFCDev] Factory Pattern
>
>
>On 11/6/05, John Farrar <[EMAIL PROTECTED]> wrote:
>> I see all the advantages you speak of... when the hosting environment
>> provides for them. Yet, when it doesn't then the applications do not run.
>
>It's very simple: vote with your pocketboot - don't use shared hosts
>that don't work properly...
>--
>Sean A Corfield -- http://corfield.org/
>Got frameworks?
>
>"If you're not annoying somebody, you're not really alive."
>-- Margaret Atwood
>
>
>----------------------------------------------------------
>You are subscribed to cfcdev. To unsubscribe, send an email to
>[email protected] with the words 'unsubscribe cfcdev' as the
>subject of the email.
>
>CFCDev is run by CFCZone (www.cfczone.org) and supported by
>CFXHosting (www.cfxhosting.com).
>
>An archive of the CFCDev list is available at
>www.mail-archive.com/[email protected]
>
>





----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to 
[email protected] with the words 'unsubscribe cfcdev' as the subject of the 
email.

CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting 
(www.cfxhosting.com).

An archive of the CFCDev list is available at 
www.mail-archive.com/[email protected]


Reply via email to