<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Amazon&#8217;s S3 Web Service, our #1 cause of failure</title>
	<link>http://blog.crowdflower.com/2008/07/amazons-s3-web-service-our-1-cause-of-failure/</link>
	<description></description>
	<pubDate>Thu, 11 Mar 2010 07:12:39 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: daven</title>
		<link>http://blog.crowdflower.com/2008/07/amazons-s3-web-service-our-1-cause-of-failure/#comment-2302</link>
		<dc:creator>daven</dc:creator>
		<pubDate>Wed, 10 Feb 2010 12:25:33 +0000</pubDate>
		<guid>http://blog.crowdflower.com/2008/07/amazons-s3-web-service-our-1-cause-of-failure/#comment-2302</guid>
		<description>I don't know if anybody's reported this before but the browser I got does not show this article rightly... It appears that a significant portion of it is not showing and the layout of your page doesn't seem right. Can you confirm that this post has been tested with Google Chrome?</description>
		<content:encoded><![CDATA[<p>I don&#8217;t know if anybody&#8217;s reported this before but the browser I got does not show this article rightly&#8230; It appears that a significant portion of it is not showing and the layout of your page doesn&#8217;t seem right. Can you confirm that this post has been tested with Google Chrome?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Usdating</title>
		<link>http://blog.crowdflower.com/2008/07/amazons-s3-web-service-our-1-cause-of-failure/#comment-2093</link>
		<dc:creator>Usdating</dc:creator>
		<pubDate>Sun, 10 Jan 2010 21:33:49 +0000</pubDate>
		<guid>http://blog.crowdflower.com/2008/07/amazons-s3-web-service-our-1-cause-of-failure/#comment-2093</guid>
		<description>There's some great tips there, just blogged about it too!</description>
		<content:encoded><![CDATA[<p>There&#8217;s some great tips there, just blogged about it too!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Святослав Маминов</title>
		<link>http://blog.crowdflower.com/2008/07/amazons-s3-web-service-our-1-cause-of-failure/#comment-1429</link>
		<dc:creator>Святослав Маминов</dc:creator>
		<pubDate>Sat, 22 Aug 2009 22:03:21 +0000</pubDate>
		<guid>http://blog.crowdflower.com/2008/07/amazons-s3-web-service-our-1-cause-of-failure/#comment-1429</guid>
		<description>Интересная тема, продолжайте. Иногда нахожу ответы, которые получить самому просто реально не хватает времени. Благодарю!</description>
		<content:encoded><![CDATA[<p>Интересная тема, продолжайте. Иногда нахожу ответы, которые получить самому просто реально не хватает времени. Благодарю!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Артем</title>
		<link>http://blog.crowdflower.com/2008/07/amazons-s3-web-service-our-1-cause-of-failure/#comment-1418</link>
		<dc:creator>Артем</dc:creator>
		<pubDate>Tue, 18 Aug 2009 23:56:49 +0000</pubDate>
		<guid>http://blog.crowdflower.com/2008/07/amazons-s3-web-service-our-1-cause-of-failure/#comment-1418</guid>
		<description>Вот это да... Куча комментов и практически ни одного по теме :)</description>
		<content:encoded><![CDATA[<p>Вот это да&#8230; Куча комментов и практически ни одного по теме :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: codediva</title>
		<link>http://blog.crowdflower.com/2008/07/amazons-s3-web-service-our-1-cause-of-failure/#comment-399</link>
		<dc:creator>codediva</dc:creator>
		<pubDate>Fri, 25 Jul 2008 02:48:44 +0000</pubDate>
		<guid>http://blog.crowdflower.com/2008/07/amazons-s3-web-service-our-1-cause-of-failure/#comment-399</guid>
		<description>I understand your frustration, however, anytime you used hosted services (even those from a trusted provider) you should plan on implementing some redundancy. I know this can be costly for small orgs, but it could have minimized the impact of this occurance.</description>
		<content:encoded><![CDATA[<p>I understand your frustration, however, anytime you used hosted services (even those from a trusted provider) you should plan on implementing some redundancy. I know this can be costly for small orgs, but it could have minimized the impact of this occurance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LusciousPainGeek</title>
		<link>http://blog.crowdflower.com/2008/07/amazons-s3-web-service-our-1-cause-of-failure/#comment-395</link>
		<dc:creator>LusciousPainGeek</dc:creator>
		<pubDate>Thu, 24 Jul 2008 08:48:32 +0000</pubDate>
		<guid>http://blog.crowdflower.com/2008/07/amazons-s3-web-service-our-1-cause-of-failure/#comment-395</guid>
		<description>Isn't this one of the risks you take in exchange for the convenience of using a centralized system like S3? Unfortunate, but bound to happen and something you need to look into when performing risk assessment.</description>
		<content:encoded><![CDATA[<p>Isn&#8217;t this one of the risks you take in exchange for the convenience of using a centralized system like S3? Unfortunate, but bound to happen and something you need to look into when performing risk assessment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ted Z</title>
		<link>http://blog.crowdflower.com/2008/07/amazons-s3-web-service-our-1-cause-of-failure/#comment-394</link>
		<dc:creator>Ted Z</dc:creator>
		<pubDate>Tue, 22 Jul 2008 19:15:35 +0000</pubDate>
		<guid>http://blog.crowdflower.com/2008/07/amazons-s3-web-service-our-1-cause-of-failure/#comment-394</guid>
		<description>Look into Akamai, they'll do this correctly (disclaimer: I've worked
for them).  Or implement their system (quickly deteriorating DNS
endpoint lookups) yourself, it's not hard if your scope is limited.
You can just have S3 be your primary and when it fails, switch DNS
over to your backup.</description>
		<content:encoded><![CDATA[<p>Look into Akamai, they&#8217;ll do this correctly (disclaimer: I&#8217;ve worked<br />
for them).  Or implement their system (quickly deteriorating DNS<br />
endpoint lookups) yourself, it&#8217;s not hard if your scope is limited.<br />
You can just have S3 be your primary and when it fails, switch DNS<br />
over to your backup.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Haney</title>
		<link>http://blog.crowdflower.com/2008/07/amazons-s3-web-service-our-1-cause-of-failure/#comment-393</link>
		<dc:creator>Ryan Haney</dc:creator>
		<pubDate>Tue, 22 Jul 2008 15:14:43 +0000</pubDate>
		<guid>http://blog.crowdflower.com/2008/07/amazons-s3-web-service-our-1-cause-of-failure/#comment-393</guid>
		<description>Have you considered using S3 as a backup provider with a local disk as cache?  I can envision software that emulates a hard disk with a caching mechanism that copies to and from S3 in the background, as files are requested / uploaded.

I do think though that you haven't load tested your own storage solution.  I have a friend that works for Seagate and hard drives fail ALL THE TIME.  It's just nature of the beast.</description>
		<content:encoded><![CDATA[<p>Have you considered using S3 as a backup provider with a local disk as cache?  I can envision software that emulates a hard disk with a caching mechanism that copies to and from S3 in the background, as files are requested / uploaded.</p>
<p>I do think though that you haven&#8217;t load tested your own storage solution.  I have a friend that works for Seagate and hard drives fail ALL THE TIME.  It&#8217;s just nature of the beast.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe</title>
		<link>http://blog.crowdflower.com/2008/07/amazons-s3-web-service-our-1-cause-of-failure/#comment-392</link>
		<dc:creator>Joe</dc:creator>
		<pubDate>Tue, 22 Jul 2008 03:05:39 +0000</pubDate>
		<guid>http://blog.crowdflower.com/2008/07/amazons-s3-web-service-our-1-cause-of-failure/#comment-392</guid>
		<description>Get a grip !!!  It's not like you're running a stock brokerage system on Wall St !

My experience is that it's not hosting computers that are the reliability issue, but the ISP who provides the connection.  Try getting any level of service guarantee is next to impossible.  When I build "five nines" systems for clients, we end up putting data centers in multiple cities using multiple carrier connections.  It costs a heck of a lot more than what Amazon charge for S3.  It's like you paid for a cheap car, so don't whinge about the rattles.</description>
		<content:encoded><![CDATA[<p>Get a grip !!!  It&#8217;s not like you&#8217;re running a stock brokerage system on Wall St !</p>
<p>My experience is that it&#8217;s not hosting computers that are the reliability issue, but the ISP who provides the connection.  Try getting any level of service guarantee is next to impossible.  When I build &#8220;five nines&#8221; systems for clients, we end up putting data centers in multiple cities using multiple carrier connections.  It costs a heck of a lot more than what Amazon charge for S3.  It&#8217;s like you paid for a cheap car, so don&#8217;t whinge about the rattles.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Striddy</title>
		<link>http://blog.crowdflower.com/2008/07/amazons-s3-web-service-our-1-cause-of-failure/#comment-391</link>
		<dc:creator>Striddy</dc:creator>
		<pubDate>Tue, 22 Jul 2008 02:06:19 +0000</pubDate>
		<guid>http://blog.crowdflower.com/2008/07/amazons-s3-web-service-our-1-cause-of-failure/#comment-391</guid>
		<description>Should've been:
Also, I don’t get the sense that FaceStat’s load is so heavy as to ... stress your other hosting service to the point of failure much.</description>
		<content:encoded><![CDATA[<p>Should&#8217;ve been:<br />
Also, I don’t get the sense that FaceStat’s load is so heavy as to &#8230; stress your other hosting service to the point of failure much.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
