<?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"
	>
<channel>
	<title>Comments on: Another service-provider infrastructure gets the hiccups</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/storage-soup/another-service-provider-infrastructure-gets-the-hiccups/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/storage-soup/another-service-provider-infrastructure-gets-the-hiccups/</link>
	<description>A SearchStorage.com blog.</description>
	<pubDate>Thu, 26 Nov 2009 01:29:00 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Amazon&#8217;s S3 crashes again; Web 2.0 goes boom &#8212; Storage Soup</title>
		<link>http://itknowledgeexchange.techtarget.com/storage-soup/another-service-provider-infrastructure-gets-the-hiccups/#comment-6943</link>
		<dc:creator>Amazon&#8217;s S3 crashes again; Web 2.0 goes boom &#8212; Storage Soup</dc:creator>
		<pubDate>Tue, 22 Jul 2008 18:23:41 +0000</pubDate>
		<guid isPermaLink="false">http://storage.blogs.techtarget.com/2008/02/15/another-service-provider-infrastructure-gets-the-hiccups/#comment-6943</guid>
		<description>[...] The biggest difference between the last time S3 crashed and this time, in my observation, is that there was a much, much bigger chain reaction this time around. Last time, I knew of only a few companies using S3, like photo hosting site SmugMug, and startups that offer online backup services using their own interfaces on the front-end and Amazon&#8217;s hardware infrastructure on the back-end. [...]</description>
		<content:encoded><![CDATA[<p>[...] The biggest difference between the last time S3 crashed and this time, in my observation, is that there was a much, much bigger chain reaction this time around. Last time, I knew of only a few companies using S3, like photo hosting site SmugMug, and startups that offer online backup services using their own interfaces on the front-end and Amazon&#8217;s hardware infrastructure on the back-end. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Beth</title>
		<link>http://itknowledgeexchange.techtarget.com/storage-soup/another-service-provider-infrastructure-gets-the-hiccups/#comment-6942</link>
		<dc:creator>Beth</dc:creator>
		<pubDate>Tue, 19 Feb 2008 18:51:30 +0000</pubDate>
		<guid isPermaLink="false">http://storage.blogs.techtarget.com/2008/02/15/another-service-provider-infrastructure-gets-the-hiccups/#comment-6942</guid>
		<description>The point of my post is that massively multi-tenant services which concentrate huge amounts of processing demand onto relatively few instances of computer technology will have some growing pains and problems as more and more people adopt the service-provider model. And that these hiccups, when they happen, because of the massive multi-tenancy, will be felt far and wide.</description>
		<content:encoded><![CDATA[<p>The point of my post is that massively multi-tenant services which concentrate huge amounts of processing demand onto relatively few instances of computer technology will have some growing pains and problems as more and more people adopt the service-provider model. And that these hiccups, when they happen, because of the massive multi-tenancy, will be felt far and wide.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad</title>
		<link>http://itknowledgeexchange.techtarget.com/storage-soup/another-service-provider-infrastructure-gets-the-hiccups/#comment-6941</link>
		<dc:creator>Brad</dc:creator>
		<pubDate>Tue, 19 Feb 2008 17:58:23 +0000</pubDate>
		<guid isPermaLink="false">http://storage.blogs.techtarget.com/2008/02/15/another-service-provider-infrastructure-gets-the-hiccups/#comment-6941</guid>
		<description>Beth, How does one service outage "echo" the other? At this point in time *NEITHER* service outage has been explained to have been caused by a storage system failure. Granted, they are both service failures.

I guess the point of your post is that any service (storage, transpo., comm., health, newspaper delivery, etc.) that you use could be less than 100% reliable.</description>
		<content:encoded><![CDATA[<p>Beth, How does one service outage &#8220;echo&#8221; the other? At this point in time *NEITHER* service outage has been explained to have been caused by a storage system failure. Granted, they are both service failures.</p>
<p>I guess the point of your post is that any service (storage, transpo., comm., health, newspaper delivery, etc.) that you use could be less than 100% reliable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ron</title>
		<link>http://itknowledgeexchange.techtarget.com/storage-soup/another-service-provider-infrastructure-gets-the-hiccups/#comment-6940</link>
		<dc:creator>Ron</dc:creator>
		<pubDate>Sat, 16 Feb 2008 06:00:13 +0000</pubDate>
		<guid isPermaLink="false">http://storage.blogs.techtarget.com/2008/02/15/another-service-provider-infrastructure-gets-the-hiccups/#comment-6940</guid>
		<description>RIM admitted to a change management failure.  Amazon hasn't really admitted to anything and their statement is generic with no pointer to any cause.
Achieving 99.999% uptime is not a technical solution but a pshyological one.  The reason is that the technology provides the uptime while the humans provide the downtime.  In this tug of ware who wins?</description>
		<content:encoded><![CDATA[<p>RIM admitted to a change management failure.  Amazon hasn&#8217;t really admitted to anything and their statement is generic with no pointer to any cause.<br />
Achieving 99.999% uptime is not a technical solution but a pshyological one.  The reason is that the technology provides the uptime while the humans provide the downtime.  In this tug of ware who wins?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- dynamic -->