<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Down For 8 Days: American Eagle&#8217;s Site Disaster</title>
	<atom:link href="http://storefrontbacktalk.com/e-commerce/down-for-8-days-american-eagles-site-disaster/feed/" rel="self" type="application/rss+xml" />
	<link>http://storefrontbacktalk.com/e-commerce/down-for-8-days-american-eagles-site-disaster/</link>
	<description>Techniques, Tools and Tirades about Retail Technology and E-Commerce</description>
	<lastBuildDate>Sun, 20 May 2012 01:49:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Gareth Evans</title>
		<link>http://storefrontbacktalk.com/e-commerce/down-for-8-days-american-eagles-site-disaster/comment-page-1/#comment-80689</link>
		<dc:creator>Gareth Evans</dc:creator>
		<pubDate>Thu, 29 Jul 2010 08:26:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.storefrontbacktalk.com/?p=5776#comment-80689</guid>
		<description>Contingency planning is frought with all sorts of pitfalls.  The suggestion about running your mobile site on &quot;mirrored versions of the key databases&quot; sounds great, aprt from in AE&#039;s case the gradual curruption of the main site&#039;s databases due to the array problem would also be &quot;mirrored&quot; onto the mobile site.
You could handle bandwidth issues by locating in the same datacentre and sharing the main site&#039;s bandwidth.  But that leaves both sites vulnerable to both a bandwidth outage or a datacentre failure (say, the power supply fails.
It reminds me of the phrase currently very popular with politians (certainly over here in the UK) &quot;it&#039;s a problem of unintended consequences&quot;.</description>
		<content:encoded><![CDATA[<p>Contingency planning is frought with all sorts of pitfalls.  The suggestion about running your mobile site on &#8220;mirrored versions of the key databases&#8221; sounds great, aprt from in AE&#8217;s case the gradual curruption of the main site&#8217;s databases due to the array problem would also be &#8220;mirrored&#8221; onto the mobile site.<br />
You could handle bandwidth issues by locating in the same datacentre and sharing the main site&#8217;s bandwidth.  But that leaves both sites vulnerable to both a bandwidth outage or a datacentre failure (say, the power supply fails.<br />
It reminds me of the phrase currently very popular with politians (certainly over here in the UK) &#8220;it&#8217;s a problem of unintended consequences&#8221;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

