<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Mashable - The Social Media Guide - Latest Comments in Amazon Offers Explanation For S3 Outage</title><link>http://mashable.disqus.com/</link><description>Internet and Technology News - Mashable is the world’s largest blog focused exclusively on Web 2.0 and Social Networking news. With more than 5 million monthly pageviews, Mashable is the most prolific blog reviewing new Web sites and services, publishing breaking news on what’s new on the web.</description><atom:link href="https://mashable.disqus.com/thread_0206/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Mon, 25 Feb 2008 13:33:42 -0000</lastBuildDate><item><title>Re: Amazon Offers Explanation For S3 Outage</title><link>http://mashable.com/2008/02/16/amazon-s3-outage-explained/#comment-5994751</link><description>&lt;p&gt;There is a very important question you have to ask yourself before deciding whether to use S3: what are you really looking for - remote storage, content delivery, or both. These are crucial to distinguish.&lt;/p&gt;&lt;p&gt;What I observe is that most people treat Amazon S3 as a content delivery service. While this is not inherently wrong, one has to notice that S3 was especially designed to be a STORAGE service.&lt;/p&gt;&lt;p&gt;The point is, since terrabyte hard drives are affordable nowadays and internet traffic grows steadily, the stress goes on content delivery rather than on storage. If you are not concerned about storage, there are much better services especially suited for content delivery.&lt;/p&gt;&lt;p&gt;&lt;a href="http://SteadyOffload.com" rel="nofollow noopener" target="_blank" title="SteadyOffload.com"&gt;SteadyOffload.com&lt;/a&gt; provides an innovative, subtle and convenient way to offload static content. The whole mechanism there is quite different from Amazon S3. Instead of permanently uploading your files to a third-party host, their cachebot crawls your site and mirrors the content in a temporary cache on their servers. Content remains stored on your server while it is being delivered from the SteadyOffload cache. The URL of the cached object on their server is dynamically generated at page loading time, very scrambled and is changing often, so you donâ€™t have to worry about hotlinking. This means that there is an almost non-existent chance that the cached content gets exposed outside of your web application.&lt;/p&gt;&lt;p&gt;Itâ€™s definitely worth trying because itâ€™s not a storage service like S3 but exactly a service for offloading static content.&lt;/p&gt;&lt;p&gt;Watch that:&lt;br&gt;&lt;a href="http://video.google.com/videoplay?docid=-8193919167634099306" rel="nofollow noopener" target="_blank" title="http://video.google.com/videoplay?docid=-8193919167634099306"&gt;http://video.google.com/vid...&lt;/a&gt; (the video shows integration with WordPress, but it is integrable with any other webpage)&lt;br&gt;&lt;a href="http://www.steadyoffload.com/" rel="nofollow noopener" target="_blank" title="http://www.steadyoffload.com/"&gt;http://www.steadyoffload.com/&lt;/a&gt;&lt;br&gt;&lt;a href="http://codex.wordpress.org/WordPress_Optimization/Offloading" rel="nofollow noopener" target="_blank" title="http://codex.wordpress.org/WordPress_Optimization/Offloading"&gt;http://codex.wordpress.org/...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Cost of bandwidth comes under $0.2 per GB - affordable, efficient and convenient. Looks like a startup but lures me very much. Definitely simpler and safer than Amazon S3.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Blagovest</dc:creator><pubDate>Mon, 25 Feb 2008 13:33:42 -0000</pubDate></item><item><title>Re: Amazon Offers Explanation For S3 Outage</title><link>http://mashable.com/2008/02/16/amazon-s3-outage-explained/#comment-5994750</link><description>&lt;p&gt;The downtime itself does not give me pause...however, the cause of it does.&lt;/p&gt;&lt;p&gt;How in the world does Google allow a couple of users to take down their whole system.  Do they not have countermeasures that can be implemented to prevent a single user from utilizing the system to that degree.  That seems fundamental in a shared system.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">E.T.Cook</dc:creator><pubDate>Mon, 18 Feb 2008 19:02:51 -0000</pubDate></item></channel></rss>