On Fri, Jan 27, 2012 at 10:43, Ben Scott <[email protected]> wrote:
> On Fri, Jan 27, 2012 at 12:52 PM, Stephen Wimberly
> <[email protected]> wrote:
>> Our web developer wants to host a web site "in house" rather
>> than with shared Unix hosting.
>
> What's the business justification for this? What's the ROI?
>
> Unless you have some kind of major web project, hosting in-house
> isn't a good idea. I'm a big *nix booster myself, but I still
> wouldn't want to host our website on-site.
>
> -- Ben
There are multiple issues here, even assuming it's a small web site -
if it's meant to be exposed to the public.
o- Security
Just because it's small, doesn't mean it's not a target.
Configuring a web service for secure operation (even if it hosts no
sensitive information) is not something to take on lightly. Configure
it incorreclty, and you *will* get hacked. Once hacked, your site
becomes a stepping stone for further maliciousness
o- Business availability
Whether hacked or not, if someone gets a wild hair and decides
your site is offensive, or for some strange reason your site becomes
wildly popular, your Internet pipe will get stuffed full, and you'll
find it very hard to operate.
Just those two would put me off putting up a site, unless there's a
very strong business case to justify the resources to do it correctly.
Kurt
~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
---
To manage subscriptions click here:
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to [email protected]
with the body: unsubscribe ntsysadmin
