<?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: Amazon&#8217;s S3 Web Service, our #1 cause of failure</title>
	<atom:link href="http://blog.crowdflower.com/2008/07/amazons-s3-web-service-our-1-cause-of-failure/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.crowdflower.com/2008/07/amazons-s3-web-service-our-1-cause-of-failure/</link>
	<description></description>
	<lastBuildDate>Wed, 07 Dec 2011 22:49:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: A Wikileaks Supporter</title>
		<link>http://blog.crowdflower.com/2008/07/amazons-s3-web-service-our-1-cause-of-failure/#comment-3614</link>
		<dc:creator>A Wikileaks Supporter</dc:creator>
		<pubDate>Sat, 11 Dec 2010 00:41:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.doloreslabs.com/2008/07/amazons-web-services-our-1-cause-of-failure/#comment-3614</guid>
		<description>This whole Wikileaks fiasco is pretty crazy. You should check out http://voteonwikileaks.com. It&#039;s a recently launched website that seems to be going viral. They got something like 50,000 visitors in the first 24 hours of launch. It&#039;s sort of like a crowdsourced collection of arguments against and for Wikileaks. As a blog owner, you&#039;d probably find some of the opinions there a good read.</description>
		<content:encoded><![CDATA[<p>This whole Wikileaks fiasco is pretty crazy. You should check out <a href="http://voteonwikileaks.com" rel="nofollow">http://voteonwikileaks.com</a>. It&#8217;s a recently launched website that seems to be going viral. They got something like 50,000 visitors in the first 24 hours of launch. It&#8217;s sort of like a crowdsourced collection of arguments against and for Wikileaks. As a blog owner, you&#8217;d probably find some of the opinions there a good read.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: myhotrevenue.com1</title>
		<link>http://blog.crowdflower.com/2008/07/amazons-s3-web-service-our-1-cause-of-failure/#comment-3612</link>
		<dc:creator>myhotrevenue.com1</dc:creator>
		<pubDate>Tue, 07 Dec 2010 22:07:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.doloreslabs.com/2008/07/amazons-web-services-our-1-cause-of-failure/#comment-3612</guid>
		<description>i tried blog.crowdflower.com  in the past and i like it, just keep it up!

i am sorry if i wrote in wrong section and please admins to move this  to another place.

i am find ways to make money on the net. what posibilities we have? have you ever tried survey sites? i
t seems to be easy to make money. i found myhotrevenue dot com in my searches. IS this legit? anyone know?</description>
		<content:encoded><![CDATA[<p>i tried blog.crowdflower.com  in the past and i like it, just keep it up!</p>
<p>i am sorry if i wrote in wrong section and please admins to move this  to another place.</p>
<p>i am find ways to make money on the net. what posibilities we have? have you ever tried survey sites? i<br />
t seems to be easy to make money. i found myhotrevenue dot com in my searches. IS this legit? anyone know?</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 isPermaLink="false">http://blog.doloreslabs.com/2008/07/amazons-web-services-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 isPermaLink="false">http://blog.doloreslabs.com/2008/07/amazons-web-services-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 isPermaLink="false">http://blog.doloreslabs.com/2008/07/amazons-web-services-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 isPermaLink="false">http://blog.doloreslabs.com/2008/07/amazons-web-services-our-1-cause-of-failure/#comment-395</guid>
		<description>Isn&#039;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 isPermaLink="false">http://blog.doloreslabs.com/2008/07/amazons-web-services-our-1-cause-of-failure/#comment-394</guid>
		<description>Look into Akamai, they&#039;ll do this correctly (disclaimer: I&#039;ve worked
for them).  Or implement their system (quickly deteriorating DNS
endpoint lookups) yourself, it&#039;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 isPermaLink="false">http://blog.doloreslabs.com/2008/07/amazons-web-services-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&#039;t load tested your own storage solution.  I have a friend that works for Seagate and hard drives fail ALL THE TIME.  It&#039;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 isPermaLink="false">http://blog.doloreslabs.com/2008/07/amazons-web-services-our-1-cause-of-failure/#comment-392</guid>
		<description>Get a grip !!!  It&#039;s not like you&#039;re running a stock brokerage system on Wall St !

My experience is that it&#039;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 &quot;five nines&quot; 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&#039;s like you paid for a cheap car, so don&#039;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 isPermaLink="false">http://blog.doloreslabs.com/2008/07/amazons-web-services-our-1-cause-of-failure/#comment-391</guid>
		<description>Should&#039;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>
	<item>
		<title>By: Striddy</title>
		<link>http://blog.crowdflower.com/2008/07/amazons-s3-web-service-our-1-cause-of-failure/#comment-390</link>
		<dc:creator>Striddy</dc:creator>
		<pubDate>Tue, 22 Jul 2008 02:04:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.doloreslabs.com/2008/07/amazons-web-services-our-1-cause-of-failure/#comment-390</guid>
		<description>I agree that this deep and long of an outage is not acceptable, even for a service with tempered service level.

However, your &quot;this months FaceStat downtimes by cause&quot; chart is disingenuous and useless. Foremost because looking at the last weeks of data immediately after a huge outage skews the picture severely. Why not show us since launch? Or several other months&#039; charts for comparison? Also, I don&#039;t get the sense that FaceStat&#039;s load is so heavy as to 

&gt; It’s astonishing that serving content off our own boxes can be more reliable than serving content off of Amazon.

Hypothetically, yes. Necessarily? No.

Are you going to get much more reliable at serving content in the next few years? No. Is going Amazon S3? Probably. 99.99% is a primary design goal, and unless I&#039;m misinformed, they&#039;ve been hitting that most months. This is obviously a disaster for them, but be real. 

Or, you know, jump ship and be sure to also write posts about how unreliable or expensive self-hosting is when it eventually bites you in the ass or becomes too costly to sustain.</description>
		<content:encoded><![CDATA[<p>I agree that this deep and long of an outage is not acceptable, even for a service with tempered service level.</p>
<p>However, your &#8220;this months FaceStat downtimes by cause&#8221; chart is disingenuous and useless. Foremost because looking at the last weeks of data immediately after a huge outage skews the picture severely. Why not show us since launch? Or several other months&#8217; charts for comparison? Also, I don&#8217;t get the sense that FaceStat&#8217;s load is so heavy as to </p>
<p>&gt; It’s astonishing that serving content off our own boxes can be more reliable than serving content off of Amazon.</p>
<p>Hypothetically, yes. Necessarily? No.</p>
<p>Are you going to get much more reliable at serving content in the next few years? No. Is going Amazon S3? Probably. 99.99% is a primary design goal, and unless I&#8217;m misinformed, they&#8217;ve been hitting that most months. This is obviously a disaster for them, but be real. </p>
<p>Or, you know, jump ship and be sure to also write posts about how unreliable or expensive self-hosting is when it eventually bites you in the ass or becomes too costly to sustain.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex Ranger</title>
		<link>http://blog.crowdflower.com/2008/07/amazons-s3-web-service-our-1-cause-of-failure/#comment-389</link>
		<dc:creator>Alex Ranger</dc:creator>
		<pubDate>Tue, 22 Jul 2008 01:45:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.doloreslabs.com/2008/07/amazons-web-services-our-1-cause-of-failure/#comment-389</guid>
		<description>Yes.  Did you read the Amazon SLA information before you started using their service?  S3 going down is the fault of Amazon&#039;s engineering team.  Your site going down is the site of yours.  You signed up and used a service that gives you tiny rebates for downtime rather than true uptime guarantees and you got what you deserved.  Quit whining.</description>
		<content:encoded><![CDATA[<p>Yes.  Did you read the Amazon SLA information before you started using their service?  S3 going down is the fault of Amazon&#8217;s engineering team.  Your site going down is the site of yours.  You signed up and used a service that gives you tiny rebates for downtime rather than true uptime guarantees and you got what you deserved.  Quit whining.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Danny Thorpe</title>
		<link>http://blog.crowdflower.com/2008/07/amazons-s3-web-service-our-1-cause-of-failure/#comment-388</link>
		<dc:creator>Danny Thorpe</dc:creator>
		<pubDate>Mon, 21 Jul 2008 21:55:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.doloreslabs.com/2008/07/amazons-web-services-our-1-cause-of-failure/#comment-388</guid>
		<description>&lt;strong&gt;Amazon S3 Down for 7 Hours; S3 Clients Looking for Exit...&lt;/strong&gt;

Lukas Biewald lays bare his frustrations with Amazon&#8217;s S3 service, particularly after the recent S3 service outtage that left his FaceStat business offline for more than 7 hours recently.  Actually, Lukas has double posted on this issue - he has...</description>
		<content:encoded><![CDATA[<p><strong>Amazon S3 Down for 7 Hours; S3 Clients Looking for Exit&#8230;</strong></p>
<p>Lukas Biewald lays bare his frustrations with Amazon&#8217;s S3 service, particularly after the recent S3 service outtage that left his FaceStat business offline for more than 7 hours recently.  Actually, Lukas has double posted on this issue &#8211; he has&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://blog.crowdflower.com/2008/07/amazons-s3-web-service-our-1-cause-of-failure/#comment-386</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Mon, 21 Jul 2008 17:46:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.doloreslabs.com/2008/07/amazons-web-services-our-1-cause-of-failure/#comment-386</guid>
		<description>Guys, cloud computing is still what should be called beta. Massively parallel systems are difficult and this is going to take a while to get right. If you put all your data on one of these sites, or pin your business model to theirs, you are asking for trouble. Don&#039;t put mission critical applications on new, unproven technology with no failover plan and then start whining that you aren&#039;t getting what you wanted. It&#039;s new, it&#039;s cool, it&#039;s going to be the future, but right now it&#039;s still going through growing pains.</description>
		<content:encoded><![CDATA[<p>Guys, cloud computing is still what should be called beta. Massively parallel systems are difficult and this is going to take a while to get right. If you put all your data on one of these sites, or pin your business model to theirs, you are asking for trouble. Don&#8217;t put mission critical applications on new, unproven technology with no failover plan and then start whining that you aren&#8217;t getting what you wanted. It&#8217;s new, it&#8217;s cool, it&#8217;s going to be the future, but right now it&#8217;s still going through growing pains.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jeremy</title>
		<link>http://blog.crowdflower.com/2008/07/amazons-s3-web-service-our-1-cause-of-failure/#comment-385</link>
		<dc:creator>jeremy</dc:creator>
		<pubDate>Mon, 21 Jul 2008 16:41:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.doloreslabs.com/2008/07/amazons-web-services-our-1-cause-of-failure/#comment-385</guid>
		<description>This is something any online business deals with, it&#039;s always better to host it yourself but not really cost effective for a business that&#039;s just starting. As a web business owner currently experiencing inexplicable down time I feel your pain.

If you&#039;re not responsible for getting it to work again it does give you an excuse to go outside for a little while.</description>
		<content:encoded><![CDATA[<p>This is something any online business deals with, it&#8217;s always better to host it yourself but not really cost effective for a business that&#8217;s just starting. As a web business owner currently experiencing inexplicable down time I feel your pain.</p>
<p>If you&#8217;re not responsible for getting it to work again it does give you an excuse to go outside for a little while.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

