<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Interconnect IT - WordPress Consultants, Web Development and Web Design &#187; web hosting</title>
	<atom:link href="http://interconnectit.com/tag/web-hosting/feed/" rel="self" type="application/rss+xml" />
	<link>http://interconnectit.com</link>
	<description></description>
	<lastBuildDate>Mon, 30 Jan 2012 15:53:44 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Managing Risks With Web Hosting</title>
		<link>http://interconnectit.com/112/managing-risk/</link>
		<comments>http://interconnectit.com/112/managing-risk/#comments</comments>
		<pubDate>Fri, 26 Oct 2007 11:29:43 +0000</pubDate>
		<dc:creator>Interconnect IT</dc:creator>
				<category><![CDATA[Hosting]]></category>
		<category><![CDATA[failures]]></category>
		<category><![CDATA[false economies]]></category>
		<category><![CDATA[mission critical]]></category>
		<category><![CDATA[risk level]]></category>
		<category><![CDATA[web hosting]]></category>

		<guid isPermaLink="false">http://liverpoolwebdesigner.wordpress.com/2007/10/26/managing-risk/</guid>
		<description><![CDATA[We&#8217;ve had some clients recently who&#8217;ve been burned by other web designers and their hosts. At first we wondered how&#8230; our own uptime so far this year, removing planned outages, has been 99.966% &#8211; ie, we had three hours downtime on a Sunday morning due to a routing problem at our hosts. It&#8217;s unusual to have even that much downtime,&#8230; <a class="more" href="http://interconnectit.com/112/managing-risk/">continue reading <span class="unicode">&#8674;</span></a>]]></description>
			<content:encoded><![CDATA[<p>We&#8217;ve had some clients recently who&#8217;ve been burned by other web designers and their hosts.  At first we wondered how&#8230; our own uptime so far this year, removing planned outages, has been 99.966% &#8211; ie, we had three hours downtime on a Sunday morning due to a routing problem at our hosts.</p>
<p>It&#8217;s unusual to have even that much downtime, but it can happen.  Machines can break, drives fail, and availability isn&#8217;t always easy to guarantee.</p>
<p>But if it&#8217;s happening a lot, or you run a mission critical website, then this can be a major issue.  Imagine spending £200k on a national advertising campaign, and the day it goes live the web server&#8217;s having a nap.  The developers are on an office day out, and the hosts put you on hold when you call.</p>
<p>In web hosting there&#8217;s an awful lot of people making false economies &#8211; they run major companies on cheap, consumer level hosting that costs perhaps £15 a month&#8230; or less!  This may be fine if the site isn&#8217;t generally that busy, but any spike in traffic and the machine won&#8217;t have the resources to keep the site going.  Not only that, but because you&#8217;re sharing a box with possibly thousands of other websites, the poor server may well be over-stuffed and overworked anyway.</p>
<p>There&#8217;s a few steps to consider when dealing with this:</p>
<ol>
<li>Properly assess risks.  If you could lose £100,000 of business when your website fails, it&#8217;s obviously wise to spend more than a few hundred pounds a year on it.  But there&#8217;s no point spending £10k a month on a site that generates very little trade, just for the sake of avoiding ten minutes of downtime.</li>
<li>Make sure what goes on the server is only ever fully tested code written by people you can trust.  <a href="http://www.interconnectit.com" title="Interconnect IT">Our own web consultancy, Interconnect IT</a> goes to great lengths to make sure the code supplied is reliable.</li>
<li>Consider bringing in house code-reviews and creating your own testing requirements.</li>
<li>Load test your server with the predicted maximum level of traffic.  If you don&#8217;t, how do you know its adequate?  And you can&#8217;t predict the load just on raw visitor numbers either &#8211; some websites are much more demanding on server resources than others.</li>
<li>Make sure the site is suitably protected from attacks by hackers and even malevolent rivals.</li>
</ol>
<p>Ultimately any website is a reflection of your business &#8211; if it&#8217;s cheap and unreliable, it&#8217;ll say that to your potential clients.</p>
]]></content:encoded>
			<wfw:commentRss>http://interconnectit.com/112/managing-risk/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

