<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" gd:etag="W/&quot;C04EQ30-cCp7ImA9WxBQEks.&quot;"><id>tag:blogger.com,1999:blog-8917329674696551431</id><updated>2010-01-11T18:05:02.358-08:00</updated><title>Scaling Out</title><subtitle type="html">Scaling out with Amazon EC2</subtitle><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://www.scalingout.com/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://www.scalingout.com/" /><link rel="next" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default?start-index=26&amp;max-results=25&amp;redirect=false&amp;v=2" /><author><name>Travis Reeder</name><uri>http://www.blogger.com/profile/01398330633165910535</uri><email>noreply@blogger.com</email></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>45</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://feeds.feedburner.com/ScalingOut" /><feedburner:info uri="scalingout" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><feedburner:emailServiceId>ScalingOut</feedburner:emailServiceId><feedburner:feedburnerHostname>http://feedburner.google.com</feedburner:feedburnerHostname><entry gd:etag="W/&quot;DE8EQXw5eSp7ImA9WxRbEUo.&quot;"><id>tag:blogger.com,1999:blog-8917329674696551431.post-4932542662763889215</id><published>2008-12-01T16:13:00.001-08:00</published><updated>2008-12-01T16:13:20.221-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-12-01T16:13:20.221-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="SimpleDB" /><category scheme="http://www.blogger.com/atom/ns#" term="Amazon" /><title>SimpleDB Open to the Public with Lower Prices</title><content type="html">&lt;p&gt;As of today, anyone can try SimpleDB with no waiting… so what are you waiting for??&lt;/p&gt;  &lt;p&gt;And they’ve reduce the storage costs by 83% to $0.25 per GB per month.&lt;/p&gt;  &lt;p&gt;AND finally (and best of all), they’ve added a FREE tier giving you 25 Machine hours + 1GB of data transfer + 1GB of storage for free. This is huge news. Now people can try and potentially use SimpleDB for free indefinitely. &lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8917329674696551431-4932542662763889215?l=www.scalingout.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ScalingOut/~4/WCKMIEDwtMc" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.scalingout.com/feeds/4932542662763889215/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8917329674696551431&amp;postID=4932542662763889215" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/4932542662763889215?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/4932542662763889215?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ScalingOut/~3/WCKMIEDwtMc/simpledb-open-to-public-with-lower.html" title="SimpleDB Open to the Public with Lower Prices" /><author><name>Travis Reeder</name><uri>http://www.blogger.com/profile/01398330633165910535</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03697593268591053185" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://www.scalingout.com/2008/12/simpledb-open-to-public-with-lower.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CEIBR3w9cCp7ImA9WxRQGUk.&quot;"><id>tag:blogger.com,1999:blog-8917329674696551431.post-1716616441193016550</id><published>2008-10-13T17:02:00.001-07:00</published><updated>2008-10-13T17:02:36.268-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-10-13T17:02:36.268-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="SimpleDB" /><category scheme="http://www.blogger.com/atom/ns#" term="S3" /><category scheme="http://www.blogger.com/atom/ns#" term="Caching" /><category scheme="http://www.blogger.com/atom/ns#" term="Amazon" /><category scheme="http://www.blogger.com/atom/ns#" term="EC2" /><title>New Social Search Product Running Completely on Amazon Web Services</title><content type="html">&lt;p&gt; A new social search service called &lt;a href="http://www.sidestripe.com"&gt;SideStripe&lt;/a&gt; has been released into the wild. The service lets you find information as well as ask questions and get answers from the people in your social network. They also have a nice widget that embeds itself right in your Google results.&lt;/p&gt;  &lt;p&gt;&lt;a href="http://www.sidestripe.com"&gt;&lt;img title="google1-ex-frompaint" style="border-right: 0px; border-top: 0px; display: inline; border-left: 0px; border-bottom: 0px" height="297" alt="google1-ex-frompaint" src="http://lh6.ggpht.com/treeder/SPPhm1or5nI/AAAAAAAARB8/SdrqCeJSLzQ/google1-ex-frompaint%5B6%5D.png?imgmax=800" width="342" border="0" /&gt;&lt;/a&gt;&amp;#160;&lt;/p&gt;  &lt;p&gt;SideStripe is running on EC2 with app servers behind load balancers, SimpleDB is the database and S3 is used for larger data that doesn’t fit in S3 as well as for shared caching.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8917329674696551431-1716616441193016550?l=www.scalingout.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ScalingOut/~4/WC1PDMFDbvY" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.scalingout.com/feeds/1716616441193016550/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8917329674696551431&amp;postID=1716616441193016550" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/1716616441193016550?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/1716616441193016550?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ScalingOut/~3/WC1PDMFDbvY/new-social-search-product-running.html" title="New Social Search Product Running Completely on Amazon Web Services" /><author><name>Travis Reeder</name><uri>http://www.blogger.com/profile/01398330633165910535</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03697593268591053185" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://www.scalingout.com/2008/10/new-social-search-product-running.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkUARnw-cSp7ImA9WxRQFUo.&quot;"><id>tag:blogger.com,1999:blog-8917329674696551431.post-2077223705960770118</id><published>2008-10-09T10:44:00.001-07:00</published><updated>2008-10-09T10:44:07.259-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-10-09T10:44:07.259-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="S3" /><category scheme="http://www.blogger.com/atom/ns#" term="Amazon" /><title>Amazon Reducing S3 Storage Costs via Tiers</title><content type="html">&lt;p&gt;Starting November 1st, the following pricing structure will take effect.&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;&lt;b&gt;Current storage price (through Oct 31, 2008)&lt;/b&gt;      &lt;br /&gt;US: $0.150 per GB      &lt;br /&gt;EU: $0.180 per GB      &lt;br /&gt;&lt;b&gt;New storage price (effective Nov 1, 2008)&lt;/b&gt;      &lt;br /&gt;US      &lt;br /&gt;$0.150 First 50 TB / month of storage used      &lt;br /&gt;$0.140 Next 50 TB / month of storage used      &lt;br /&gt;$0.130 Next 400 TB / month of storage used      &lt;br /&gt;$0.120 Storage used / month over 500 TB      &lt;br /&gt;EU      &lt;br /&gt;$0.180 First 50 TB / month of storage used      &lt;br /&gt;$0.170 Next 50 TB / month of storage used      &lt;br /&gt;$0.160 Next 400 TB / month of storage used      &lt;br /&gt;$0.150 Storage used / month over 500 TB&lt;/p&gt; &lt;/blockquote&gt;  &lt;p&gt;I’m still hoping that they drop the per request price at some point.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8917329674696551431-2077223705960770118?l=www.scalingout.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ScalingOut/~4/7NLqhfjXq0s" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.scalingout.com/feeds/2077223705960770118/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8917329674696551431&amp;postID=2077223705960770118" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/2077223705960770118?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/2077223705960770118?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ScalingOut/~3/7NLqhfjXq0s/amazon-reducing-s3-storage-costs-via.html" title="Amazon Reducing S3 Storage Costs via Tiers" /><author><name>Travis Reeder</name><uri>http://www.blogger.com/profile/01398330633165910535</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03697593268591053185" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://www.scalingout.com/2008/10/amazon-reducing-s3-storage-costs-via.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUMHQHszfCp7ImA9WxRRGEo.&quot;"><id>tag:blogger.com,1999:blog-8917329674696551431.post-5150940970262606171</id><published>2008-10-01T08:03:00.001-07:00</published><updated>2008-10-01T08:03:51.584-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-10-01T08:03:51.584-07:00</app:edited><title>EC2 to Support Microsoft Windows Server and SQL Server this Fall</title><content type="html">&lt;p&gt;Currently EC2 only supports Unix based operating systems, but coming this fall you’ll be able to run Windows Servers. This may not sound like much, but sometimes you just need it and it will be nice to be able to have it. We needed Windows as part of our infrastructure for one project and we actually we had to lease a windows box from another host and send messages between them to get things done… not pretty. This should solve that problem.&lt;/p&gt;  &lt;p&gt;This is also great news for you ASP.NET developers. Welcome to the cloud!&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8917329674696551431-5150940970262606171?l=www.scalingout.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ScalingOut/~4/MxmmSLFTj-M" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.scalingout.com/feeds/5150940970262606171/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8917329674696551431&amp;postID=5150940970262606171" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/5150940970262606171?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/5150940970262606171?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ScalingOut/~3/MxmmSLFTj-M/ec2-to-support-microsoft-windows-server.html" title="EC2 to Support Microsoft Windows Server and SQL Server this Fall" /><author><name>Travis Reeder</name><uri>http://www.blogger.com/profile/01398330633165910535</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03697593268591053185" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://www.scalingout.com/2008/10/ec2-to-support-microsoft-windows-server.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUMEQHo-fip7ImA9WxRSF0g.&quot;"><id>tag:blogger.com,1999:blog-8917329674696551431.post-5250345748039244149</id><published>2008-09-18T10:03:00.001-07:00</published><updated>2008-09-18T10:03:21.456-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-09-18T10:03:21.456-07:00</app:edited><title>Amazon Will Soon Have a CDN</title><content type="html">&lt;p&gt;Wow, the hits just keep on coming. Amazon is quickly becoming the one stop shop for every possible hosting scenario. They will soon add a content delivery network for low latency delivery for things such as video's, etc. &lt;/p&gt;  &lt;p&gt;I love how easy it will be to use. Just upload your file to S3 like you do now and then a single API call will make it part of the CDN. &lt;/p&gt;  &lt;p&gt;&lt;a href="http://www.amazon.com/gp/html-forms-controller/aws-content-delivery-service?"&gt;Read more...&lt;/a&gt;&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8917329674696551431-5250345748039244149?l=www.scalingout.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ScalingOut/~4/oLOyevU0JXE" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.scalingout.com/feeds/5250345748039244149/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8917329674696551431&amp;postID=5250345748039244149" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/5250345748039244149?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/5250345748039244149?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ScalingOut/~3/oLOyevU0JXE/amazon-will-soon-have-cdn.html" title="Amazon Will Soon Have a CDN" /><author><name>Travis Reeder</name><uri>http://www.blogger.com/profile/01398330633165910535</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03697593268591053185" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://www.scalingout.com/2008/09/amazon-will-soon-have-cdn.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkECQX4-eSp7ImA9WxRTEU4.&quot;"><id>tag:blogger.com,1999:blog-8917329674696551431.post-5669371042292776529</id><published>2008-08-30T15:17:00.001-07:00</published><updated>2008-08-30T15:17:40.051-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-08-30T15:17:40.051-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Scalability" /><category scheme="http://www.blogger.com/atom/ns#" term="S3" /><category scheme="http://www.blogger.com/atom/ns#" term="Caching" /><category scheme="http://www.blogger.com/atom/ns#" term="Amazon" /><title>Use Amazon S3 like Memcached</title><content type="html">&lt;p&gt;A new open source project called CloudCache enables people to use a simple cache/map interface into Amazon S3. Check it out at:&lt;/p&gt;  &lt;p&gt;&lt;a title="http://code.google.com/p/cloudcache/" href="http://code.google.com/p/cloudcache/"&gt;http://code.google.com/p/cloudcache/&lt;/a&gt;&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8917329674696551431-5669371042292776529?l=www.scalingout.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ScalingOut/~4/y0oe9mppVRQ" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.scalingout.com/feeds/5669371042292776529/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8917329674696551431&amp;postID=5669371042292776529" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/5669371042292776529?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/5669371042292776529?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ScalingOut/~3/y0oe9mppVRQ/use-amazon-s3-like-memcached.html" title="Use Amazon S3 like Memcached" /><author><name>Travis Reeder</name><uri>http://www.blogger.com/profile/01398330633165910535</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03697593268591053185" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://www.scalingout.com/2008/08/use-amazon-s3-like-memcached.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0QAQX84fSp7ImA9WxdWFEk.&quot;"><id>tag:blogger.com,1999:blog-8917329674696551431.post-1921175755172937909</id><published>2008-07-01T11:12:00.001-07:00</published><updated>2008-07-07T09:49:00.135-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-07-07T09:49:00.135-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="SimpleDB" /><category scheme="http://www.blogger.com/atom/ns#" term="Pricing" /><category scheme="http://www.blogger.com/atom/ns#" term="Amazon" /><category scheme="http://www.blogger.com/atom/ns#" term="EC2" /><title>How Much Would it Cost to run Twitter on Amazon's SimpleDB?</title><content type="html">&lt;p&gt;As you may or may not know, Twitter has had an &lt;a href="http://www.techcrunch.com/2008/06/06/twitter-suffers-minor-period-of-uptime-overnight/"&gt;amazing&lt;/a&gt; &lt;a href="http://www.techcrunch.com/2008/06/27/conversations-come-to-a-screaming-halt-on-twitter-users-simply-move-to-friendfeed/"&gt;amount&lt;/a&gt; of &lt;a href="http://www.techcrunch.com/2008/06/06/hey-twitter-maybe-its-better-not-to-share-absolutely-everything/"&gt;downtime&lt;/a&gt; in the past few months and it may be due in part to running only &lt;a href="http://www.techcrunch.com/2008/06/08/twitter-tempts-fate/"&gt;three MySQL servers&lt;/a&gt; to run one of the most popular sites on the Internet. So lets say they wanted to use SimpleDB to get rid of their database issues, well lets try to figure out their costs based on some publicly available &lt;a href="http://www.techcrunch.com/2008/04/29/end-of-speculation-the-real-twitter-usage-numbers/"&gt;usage numbers&lt;/a&gt; and &lt;a href="http://siteanalytics.compete.com/twitter.com/?metric=uv"&gt;traffic numbers&lt;/a&gt; along with these &lt;a href="http://www.scalingout.com/2008/06/simpledb-boxusage-calculations.html"&gt;BoxUsage numbers&lt;/a&gt;. &lt;/p&gt;  &lt;p&gt;Twitter Usage&lt;/p&gt;  &lt;p&gt;&lt;u&gt;March 2008&lt;/u&gt;     &lt;br /&gt;Total Users: 1+ million     &lt;br /&gt;Total Active Users: 200,000 per week     &lt;br /&gt;Total Twitter Messages: 3 million/day&lt;/p&gt;  &lt;p&gt;14 Million Visits per month with an average of 7 pages per visit = 98 million pageviews per month&lt;/p&gt;  &lt;p&gt;Now lets assume that each page only does one (assume a small amount of caching) and each object has item has 5 attributes.&lt;/p&gt;  &lt;p&gt;Translated to SimpleDB usage:&lt;/p&gt;  &lt;ul&gt;   &lt;li&gt;3 million PUT's per day &lt;/li&gt;    &lt;li&gt;98 million QUERY's per month&lt;/li&gt;    &lt;li&gt;98 million GET's per month&lt;/li&gt; &lt;/ul&gt;  &lt;p&gt;3 million PUT's = (3 * $3.079) + (3 * 0.0000280 * 5^3) = $9.25 / day = $277.43 / month&lt;/p&gt;  &lt;p&gt;98 million QUERY's = (98 * $1.96) + (98 * 0.00112 * 5) = $192.63 / month&lt;/p&gt;  &lt;p&gt;98 million GET's = (98 * $1.305) + (98 * 0.00028 * 5^2) = $128.58 / month&lt;/p&gt;  &lt;p&gt;&lt;font size="3"&gt;For a grand total of &lt;strong&gt;$598.64 per month&lt;/strong&gt;.&lt;/font&gt;&lt;/p&gt;  &lt;p&gt;This only includes box usage for SimpleDB and does not include bandwidth (which is free if you're using EC2) or storage.&lt;/p&gt;  &lt;p&gt;Wow, a lot cheaper than I would have expected. Also, you could reduce this cost significantly by doing some serious caching (if you develop in Java, check out &lt;a href="http://code.google.com/p/simplejpa/"&gt;SimpleJPA&lt;/a&gt; to get easy caching). &lt;/p&gt;  &lt;p&gt;UPDATE: I miscalculated this when I first posted it by counting 98 million pageviews per day, when it should be per month. Should be all corrected now.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8917329674696551431-1921175755172937909?l=www.scalingout.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ScalingOut/~4/B2Q2d0FJk2o" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.scalingout.com/feeds/1921175755172937909/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8917329674696551431&amp;postID=1921175755172937909" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/1921175755172937909?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/1921175755172937909?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ScalingOut/~3/B2Q2d0FJk2o/how-much-would-it-cost-to-run-twitter.html" title="How Much Would it Cost to run Twitter on Amazon&amp;#39;s SimpleDB?" /><author><name>Travis Reeder</name><uri>http://www.blogger.com/profile/01398330633165910535</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03697593268591053185" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://www.scalingout.com/2008/07/how-much-would-it-cost-to-run-twitter.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUECRXw_fip7ImA9WxdXGEo.&quot;"><id>tag:blogger.com,1999:blog-8917329674696551431.post-7241400844498323191</id><published>2008-06-30T19:01:00.001-07:00</published><updated>2008-06-30T19:01:04.246-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-06-30T19:01:04.246-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="SimpleDB" /><category scheme="http://www.blogger.com/atom/ns#" term="Amazon" /><title>SimpleDB BoxUsage Calculations</title><content type="html">&lt;p&gt;Colin Percival wrote &lt;a href="http://www.daemonology.net/blog/2008-06-25-dissecting-simpledb-boxusage.html"&gt;a great article that dissects SimpleDB's BoxUsage figures&lt;/a&gt;. It's very interesting what he found and he breaks it down in a nice table that you can use to estimate how much using SimpleDB will cost you. &lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8917329674696551431-7241400844498323191?l=www.scalingout.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ScalingOut/~4/2bApuhCLmLQ" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.scalingout.com/feeds/7241400844498323191/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8917329674696551431&amp;postID=7241400844498323191" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/7241400844498323191?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/7241400844498323191?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ScalingOut/~3/2bApuhCLmLQ/simpledb-boxusage-calculations.html" title="SimpleDB BoxUsage Calculations" /><author><name>Travis Reeder</name><uri>http://www.blogger.com/profile/01398330633165910535</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03697593268591053185" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://www.scalingout.com/2008/06/simpledb-boxusage-calculations.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0ADQH46fyp7ImA9WxZbEUg.&quot;"><id>tag:blogger.com,1999:blog-8917329674696551431.post-6511256217407852587</id><published>2008-04-06T10:15:00.001-07:00</published><updated>2008-04-13T23:49:31.017-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-04-13T23:49:31.017-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="SimpleDB" /><category scheme="http://www.blogger.com/atom/ns#" term="BigTable" /><category scheme="http://www.blogger.com/atom/ns#" term="TechCrunch" /><category scheme="http://www.blogger.com/atom/ns#" term="MapReduce" /><category scheme="http://www.blogger.com/atom/ns#" term="Google" /><category scheme="http://www.blogger.com/atom/ns#" term="Amazon" /><category scheme="http://www.blogger.com/atom/ns#" term="Competitors" /><category scheme="http://www.blogger.com/atom/ns#" term="GFS" /><title>Google Plans to Launch BigTable as a Service</title><content type="html">Google's &lt;a href="http://andrewhitchcock.org/?post=214"&gt;BigTable&lt;/a&gt; might be open to the public soon, &lt;a href="http://www.techcrunch.com/2008/04/04/source-google-to-launch-bigtable-as-web-service/"&gt;so says TechCrunch&lt;/a&gt;, essentially competing directly with Amazon's recently launched &lt;a href="http://www.scalingout.com/2007/12/amazon-rolls-out-missing-piece-to-its.html"&gt;SimpleDB&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;BigTable is a massively scalable database and it is what Google uses for over 60 of their own applications including Google Maps and Orkut.&lt;br /&gt;&lt;blockquote&gt;BigTable allows Google to have a very small incremental cost for new services and expanded computing power (they don't have to buy a license for every machine, for example). BigTable is built atop their other services, specifically GFS, Scheduler, Lock Service, and MapReduce.&lt;/blockquote&gt;This is a huge move from Google that I hope we see more of in the near future... is an EC2 clone on the way?&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8917329674696551431-6511256217407852587?l=www.scalingout.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ScalingOut/~4/N34VVborsIo" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.scalingout.com/feeds/6511256217407852587/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8917329674696551431&amp;postID=6511256217407852587" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/6511256217407852587?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/6511256217407852587?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ScalingOut/~3/N34VVborsIo/google-plans-to-launch-bigtable-as.html" title="Google Plans to Launch BigTable as a Service" /><author><name>Travis Reeder</name><uri>http://www.blogger.com/profile/01398330633165910535</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03697593268591053185" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://www.scalingout.com/2008/04/google-plans-to-launch-bigtable-as.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0ICQnk9eCp7ImA9WxZVFkk.&quot;"><id>tag:blogger.com,1999:blog-8917329674696551431.post-1681519150753486305</id><published>2008-03-27T11:12:00.001-07:00</published><updated>2008-03-27T11:12:43.760-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-03-27T11:12:43.760-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="High Availability" /><category scheme="http://www.blogger.com/atom/ns#" term="Availability Zones" /><category scheme="http://www.blogger.com/atom/ns#" term="Amazon" /><category scheme="http://www.blogger.com/atom/ns#" term="EC2" /><title>EC2 Availability Zones Protect Your Applications from Data Center Outages</title><content type="html">&lt;p&gt;Amazon just released another new feature for the &lt;a href="http://www.amazon.com/b/ref=sc_fe_c_1_3435361_2?ie=UTF8&amp;amp;node=201590011&amp;amp;no=3435361&amp;amp;me=A36L942TSJ2AJA"&gt;Elastic Compute Cloud&lt;/a&gt; that allows you to specify physically different locations when launching an EC2 instance. It's called &lt;a href="http://developer.amazonwebservices.com/connect/entry.jspa?externalID=1347"&gt;Availability Zones&lt;/a&gt;. This means that if there is a major data center issue such as a network outage or even a fire in one Availability Zone, it will not affect an instance running in a different zone. High availability on the cheap... a beautiful thing.&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;&amp;quot;Previously, only very large companies had the scale to be able to distribute an application across multiple locations, but now it is as easy as changing a parameter in an API call.&amp;quot;&lt;/p&gt;&lt;/blockquote&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8917329674696551431-1681519150753486305?l=www.scalingout.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ScalingOut/~4/aaA7WV_XuM4" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.scalingout.com/feeds/1681519150753486305/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8917329674696551431&amp;postID=1681519150753486305" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/1681519150753486305?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/1681519150753486305?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ScalingOut/~3/aaA7WV_XuM4/ec2-availability-zones-protect-your.html" title="EC2 Availability Zones Protect Your Applications from Data Center Outages" /><author><name>Travis Reeder</name><uri>http://www.blogger.com/profile/01398330633165910535</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03697593268591053185" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://www.scalingout.com/2008/03/ec2-availability-zones-protect-your.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Ck4HR3k7eip7ImA9WxZVFkk.&quot;"><id>tag:blogger.com,1999:blog-8917329674696551431.post-4596464237388843653</id><published>2008-03-27T11:02:00.001-07:00</published><updated>2008-03-27T11:02:16.702-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-03-27T11:02:16.702-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Elastic IP" /><category scheme="http://www.blogger.com/atom/ns#" term="Dynamic DNS" /><category scheme="http://www.blogger.com/atom/ns#" term="Amazon" /><category scheme="http://www.blogger.com/atom/ns#" term="EC2" /><title>Amazon EC2 Now Has Static IP Addresses</title><content type="html">&lt;p&gt;Or as they like to call them, &lt;a href="http://www.amazon.com/gp/r.html?R=4ISHBDFR1YXY&amp;amp;C=3GR44HSX8PCXZ&amp;amp;H=5yjYhMiEfagqpDojhs4IuHjAOmIA&amp;amp;T=C&amp;amp;U=http%3A%2F%2Fwww.amazon.com%2Fgp%2Fredirect.html%2Fref%3Dpe_12300_8798110_aws_ec2_EIPeipfg%3Flocation%3Dhttp%253A%2F%2Fdeveloper.amazonwebservices.com%2Fconnect%2Fentry.jspa%253FexternalID%253D1346%26token%3D739460D8DF5E232AC1BAB0F33CAD7AED8FC4A56F"&gt;Elastic IP Addresses&lt;/a&gt;. It is actually a pretty interesting concept that allows you to get a static IP address assigned to your account which you can then point to any particular EC2 instance. So if you take a server down, you point the Elastic IP to a new instance and the outside world still uses the same IP. Here's Amazon's description:&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;Elastic IP addresses are static IP addresses designed for dynamic cloud computing. An Elastic IP address is associated with your account not a particular instance, and you control that address until you choose to explicitly release it. Unlike traditional static IP addresses, however, Elastic IP addresses allow you to mask instance or Availability Zone failures by programmatically remapping your public IP addresses to any instance in your account. Rather than waiting on a data technician to reconfigure or replace your host, or waiting for DNS to propagate to all of your customers, Amazon EC2 enables you to engineer around problems with your instance or software by quickly remapping your Elastic IP address to a replacement instance. &lt;/p&gt; &lt;/blockquote&gt;  &lt;p&gt;Of course, you can still use &lt;a href="http://blog.spaceprogram.com/2008/03/how-to-set-up-dynamic-dns-for-your.html"&gt;dynamic dns (explained here)&lt;/a&gt; too.&lt;/p&gt;  &lt;p&gt;Pricing:&lt;/p&gt;  &lt;p&gt;No cost for Elastic IP addresses while in use   &lt;br /&gt;$0.01 per hour when &lt;strong&gt;not&lt;/strong&gt; mapped to a running instance    &lt;br /&gt;100 free Elastic IP remaps per month per account and $.10 per remap thereafter&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8917329674696551431-4596464237388843653?l=www.scalingout.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ScalingOut/~4/eiaq1hiYTw8" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.scalingout.com/feeds/4596464237388843653/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8917329674696551431&amp;postID=4596464237388843653" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/4596464237388843653?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/4596464237388843653?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ScalingOut/~3/eiaq1hiYTw8/amazon-ec2-now-has-static-ip-addresses.html" title="Amazon EC2 Now Has Static IP Addresses" /><author><name>Travis Reeder</name><uri>http://www.blogger.com/profile/01398330633165910535</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03697593268591053185" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total><feedburner:origLink>http://www.scalingout.com/2008/03/amazon-ec2-now-has-static-ip-addresses.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkENSHk_eSp7ImA9WxZXGE4.&quot;"><id>tag:blogger.com,1999:blog-8917329674696551431.post-6160783963008931523</id><published>2008-03-06T12:18:00.001-08:00</published><updated>2008-03-06T12:18:19.741-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-03-06T12:18:19.741-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="SimpleDB" /><category scheme="http://www.blogger.com/atom/ns#" term="BigTable" /><category scheme="http://www.blogger.com/atom/ns#" term="Database" /><category scheme="http://www.blogger.com/atom/ns#" term="SSDS" /><category scheme="http://www.blogger.com/atom/ns#" term="Scaling" /><category scheme="http://www.blogger.com/atom/ns#" term="Amazon" /><category scheme="http://www.blogger.com/atom/ns#" term="SQL Server" /><category scheme="http://www.blogger.com/atom/ns#" term="Microsoft" /><category scheme="http://www.blogger.com/atom/ns#" term="Cloud Computing" /><title>Microsoft Responds to Amazon SimpleDB with SQL Server Data Services (SSDS)</title><content type="html">&lt;p&gt;There's not a lot of information on what exactly this will be (relational db? bigtableish? will it even be SQL Server behind the scenes?) other than &lt;a href="http://www.microsoft.com/sql/dataservices/faq.mspx"&gt;users can host an unlimited amount of data on SSDS&lt;/a&gt;. My guess is it's not relational and not SQL Server, but rather more like &lt;a href="http://en.wikipedia.org/wiki/BigTable"&gt;BigTable&lt;/a&gt;/&lt;a href="http://www.amazon.com/b?ie=UTF8&amp;amp;node=342335011"&gt;SimpleDB&lt;/a&gt; since that appears to be the new school way of massively scaling your data like how the big green giant Google does it. &lt;/p&gt;  &lt;p&gt;They do have some interesting features that take the edge over SimpleDB such as full-text search and a &lt;a href="http://msdn2.microsoft.com/en-us/netframework/aa904594.aspx"&gt;LINQ&lt;/a&gt; based query language. &lt;/p&gt;  &lt;p&gt;You can &lt;a href="http://www.microsoft.com/sql/dataservices/default.mspx"&gt;get your name on the beta list here&lt;/a&gt;. &lt;/p&gt;  &lt;p&gt;Why is it that when Microsoft does something like this, it's just not quite as exciting as when a different company does it? If Google announced something like this instead of Microsoft, I would be so much more excited. Oh well, at least it's good to see some competition cropping up.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8917329674696551431-6160783963008931523?l=www.scalingout.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ScalingOut/~4/uU0Qcfd37HE" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.scalingout.com/feeds/6160783963008931523/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8917329674696551431&amp;postID=6160783963008931523" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/6160783963008931523?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/6160783963008931523?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ScalingOut/~3/uU0Qcfd37HE/microsoft-responds-to-amazon-simpledb.html" title="Microsoft Responds to Amazon SimpleDB with SQL Server Data Services (SSDS)" /><author><name>Travis Reeder</name><uri>http://www.blogger.com/profile/01398330633165910535</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03697593268591053185" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://www.scalingout.com/2008/03/microsoft-responds-to-amazon-simpledb.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkQBRnYzfCp7ImA9WxZXE0w.&quot;"><id>tag:blogger.com,1999:blog-8917329674696551431.post-2573535591043525974</id><published>2008-02-29T11:45:00.001-08:00</published><updated>2008-02-29T11:45:57.884-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-02-29T11:45:57.884-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Amazon" /><category scheme="http://www.blogger.com/atom/ns#" term="EC2" /><title>Smugmug says Amazon EC2 is not Slower than they Advertise - it just Depends on How you Define a GHz</title><content type="html">&lt;blockquote&gt;   &lt;p&gt;&lt;strong&gt;All GHz aren&amp;#8217;t created equal.&lt;/strong&gt;&lt;/p&gt; &lt;/blockquote&gt;  &lt;p&gt;Who knew? &lt;a href="http://blogs.smugmug.com/don/2008/02/27/ec2-isnt-50-slower/"&gt;Here's a good read backed by real numbers&lt;/a&gt; by one of the most notable Amazon customers &lt;a href="http://www.smugmug.com"&gt;Smugmug&lt;/a&gt;, not by &lt;a href="http://developer.amazonwebservices.com/connect/thread.jspa?messageID=69066්"&gt;people complaining in the forums&lt;/a&gt;.&amp;#160; &lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8917329674696551431-2573535591043525974?l=www.scalingout.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ScalingOut/~4/UGl71AUx3oU" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.scalingout.com/feeds/2573535591043525974/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8917329674696551431&amp;postID=2573535591043525974" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/2573535591043525974?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/2573535591043525974?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ScalingOut/~3/UGl71AUx3oU/smugmug-says-amazon-ec2-is-not-slower.html" title="Smugmug says Amazon EC2 is not Slower than they Advertise - it just Depends on How you Define a GHz" /><author><name>Travis Reeder</name><uri>http://www.blogger.com/profile/01398330633165910535</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03697593268591053185" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://www.scalingout.com/2008/02/smugmug-says-amazon-ec2-is-not-slower.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUANQnsyfip7ImA9WxZXE0w.&quot;"><id>tag:blogger.com,1999:blog-8917329674696551431.post-2421935936004184756</id><published>2008-02-29T11:36:00.001-08:00</published><updated>2008-02-29T11:36:33.596-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-02-29T11:36:33.596-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="S3" /><category scheme="http://www.blogger.com/atom/ns#" term="Supercomputing" /><category scheme="http://www.blogger.com/atom/ns#" term="Amazon" /><category scheme="http://www.blogger.com/atom/ns#" term="EC2" /><category scheme="http://www.blogger.com/atom/ns#" term="Hadoop" /><title>The Future Just Called...</title><content type="html">&lt;p&gt;I had a written a post back in November about &lt;a href="http://www.scalingout.com/2007/11/new-york-times-uses-ec2-and-s3-to.html"&gt;how the New York Times converted 11 million old articles to pdf in under 24 hours using Amazon EC2, S3 and Hadoop&lt;/a&gt; and then I came across &lt;a href="http://blog.case.edu/jeremy.smith/2008/02/25/generating_11_million_pdfs_with_s3_ec2_and_hadoop"&gt; a post&lt;/a&gt; today that had this to say about it:&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;The future just called and wanted to explain how &amp;quot;&lt;a href="http://en.wikipedia.org/wiki/Supercomputing#Modern_supercomputer_architecture"&gt;supercomputing&lt;/a&gt;&amp;quot; was actually going to work.&lt;/p&gt;&lt;/blockquote&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8917329674696551431-2421935936004184756?l=www.scalingout.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ScalingOut/~4/rjUSlhJkCeg" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.scalingout.com/feeds/2421935936004184756/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8917329674696551431&amp;postID=2421935936004184756" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/2421935936004184756?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/2421935936004184756?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ScalingOut/~3/rjUSlhJkCeg/future-just-called.html" title="The Future Just Called..." /><author><name>Travis Reeder</name><uri>http://www.blogger.com/profile/01398330633165910535</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03697593268591053185" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://www.scalingout.com/2008/02/future-just-called.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CE4CRno_fyp7ImA9WxZQEkU.&quot;"><id>tag:blogger.com,1999:blog-8917329674696551431.post-2313747410803691241</id><published>2008-02-17T13:16:00.001-08:00</published><updated>2008-02-17T13:16:07.447-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-02-17T13:16:07.447-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Downtime" /><category scheme="http://www.blogger.com/atom/ns#" term="S3" /><category scheme="http://www.blogger.com/atom/ns#" term="Availability" /><category scheme="http://www.blogger.com/atom/ns#" term="Outage" /><category scheme="http://www.blogger.com/atom/ns#" term="Amazon" /><title>Amazon S3 Goes Down for 3 Hours</title><content type="html">&lt;p&gt;Amazon's Simple Storage Service (S3) had it's first major outage in years going down for 3+ hours and taking down 1000's of web 2.0 sites with it. Many new companies rely on Amazon's services to run their business so when Amazon goes down, they go down (myself included). &lt;/p&gt;  &lt;p&gt;There is a &lt;a href="http://developer.amazonwebservices.com/connect/message.jspa?messageID=79982#79982"&gt;big thread that you can read about it on the AWS forums and see Amazon's Post Mortem response&lt;/a&gt;:&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;Here&amp;#8217;s some additional detail about the problem we experienced earlier today.      &lt;br /&gt;Early this morning, at 3:30am PST, we started seeing elevated levels of authenticated requests from multiple users in one of our locations.&amp;#160; While we carefully monitor our overall request volumes and these remained within normal ranges, we had not been monitoring the proportion of authenticated requests.&amp;#160; Importantly, these cryptographic requests consume more resources per call than other request types.       &lt;br /&gt;Shortly before 4:00am PST, we began to see several other users significantly increase their volume of authenticated calls.&amp;#160; The last of these pushed the authentication service over its maximum capacity before we could complete putting new capacity in place.&amp;#160; In addition to processing authenticated requests, the authentication service also performs account validation on every request Amazon S3 handles.&amp;#160; This caused Amazon S3 to be unable to process any requests in that location, beginning at 4:31am PST.&amp;#160; By 6:48am PST, we had moved enough capacity online to resolve the issue.       &lt;br /&gt;As we said earlier today, though we're proud of our uptime track record over the past two years with this service, any amount of downtime is unacceptable.&amp;#160; As part of the post mortem for this event, we have identified a set of short-term actions as well as longer term improvements.&amp;#160; We are taking immediate action on the following:&amp;#160; (a) improving our monitoring of the proportion of authenticated requests; (b) further increasing our authentication service capacity; and (c) adding additional defensive measures around the authenticated calls.&amp;#160; Additionally, we&amp;#8217;ve begun work on a service health dashboard, and expect to release that shortly.       &lt;br /&gt;Sincerely,       &lt;br /&gt;The Amazon Web Services Team &lt;/p&gt; &lt;/blockquote&gt;  &lt;p&gt;Of course it's bad that this happened, but really not so bad when you think about it. How fast could you recover your own database and servers when they go down? And we all know, things go down at some point or another. And since Amazon puts out the fires, you get to keep more of your hair.&lt;/p&gt;  &lt;p&gt;via: &lt;a href="http://weblog.infoworld.com/virtualization/archives/2008/02/amazons_s3_data.html"&gt;InfoWorld&lt;/a&gt;&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8917329674696551431-2313747410803691241?l=www.scalingout.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ScalingOut/~4/wUl84xNgLY0" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.scalingout.com/feeds/2313747410803691241/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8917329674696551431&amp;postID=2313747410803691241" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/2313747410803691241?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/2313747410803691241?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ScalingOut/~3/wUl84xNgLY0/amazon-s3-goes-down-for-3-hours.html" title="Amazon S3 Goes Down for 3 Hours" /><author><name>Travis Reeder</name><uri>http://www.blogger.com/profile/01398330633165910535</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03697593268591053185" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://www.scalingout.com/2008/02/amazon-s3-goes-down-for-3-hours.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkYGRnw7fyp7ImA9WxZRE08.&quot;"><id>tag:blogger.com,1999:blog-8917329674696551431.post-2515550040415863555</id><published>2008-02-06T10:55:00.001-08:00</published><updated>2008-02-06T10:55:27.207-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-02-06T10:55:27.207-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Simple Queue Service" /><category scheme="http://www.blogger.com/atom/ns#" term="Typica" /><category scheme="http://www.blogger.com/atom/ns#" term="SQS" /><category scheme="http://www.blogger.com/atom/ns#" term="Pricing" /><category scheme="http://www.blogger.com/atom/ns#" term="Amazon" /><title>Amazon Drops the Price for Simple Queue Service (SQS), but there are some Caveats</title><content type="html">&lt;p&gt;Amazon &lt;a href="http://developer.amazonwebservices.com/connect/entry.jspa?externalID=1148"&gt;announced a new pricing model for their Simple Queue Service (SQS)&lt;/a&gt; today which looks much more reasonable than the old system.&lt;/p&gt;  &lt;p&gt;Here are the pricing changes:&lt;/p&gt;  &lt;blockquote&gt;   &lt;h4&gt;Previous Price (prior to February 6, 2008)&lt;/h4&gt;    &lt;p&gt;&lt;b&gt;Messages&lt;/b&gt;&lt;/p&gt;    &lt;p&gt;$0.10 per 1,000 messages sent ($0.0001 per message sent)&lt;/p&gt;    &lt;p&gt;&lt;b&gt;Data Transfer&lt;/b&gt;&lt;/p&gt;    &lt;p&gt;$0.10 per GB&amp;#8212;all data transfer in      &lt;br /&gt;$0.18 per GB&amp;#8212;first 10 TB / month data transfer out       &lt;br /&gt;$0.16 per GB&amp;#8212;next 40 TB / month data transfer out       &lt;br /&gt;$0.13 per GB&amp;#8212;data transfer out / month over 50 TB&lt;/p&gt;    &lt;h4&gt;New Price (effective February 6, 2008)&lt;/h4&gt;    &lt;p&gt;&lt;b&gt;Requests&lt;/b&gt;&lt;/p&gt;    &lt;p&gt;$0.01 per 10,000 Amazon SQS requests ($0.000001 per request)&lt;/p&gt;    &lt;p&gt;&lt;b&gt;Data Transfer&lt;/b&gt;&lt;/p&gt;    &lt;p&gt;Data transfer rates are unchanged. However, because many customers want to use Amazon SQS in conjunction with Amazon EC2,&lt;strong&gt;&lt;font color="#00ffff"&gt; &lt;/font&gt;&lt;font color="#0080ff"&gt;all data transferred between Amazon EC2 and Amazon SQS is &lt;i&gt;free of charge&lt;/i&gt;&lt;/font&gt;&lt;/strong&gt;.&lt;/p&gt; &lt;/blockquote&gt;  &lt;p&gt;So to get the benefits, you should use EC2 to get the free data transfer and second, poll the queue as little as possible (throttle back if the queue is empty and pick it up when there's stuff in it again).&lt;/p&gt;  &lt;h4&gt;&lt;strong&gt;&lt;/strong&gt;&lt;/h4&gt;  &lt;h4&gt;Message Retention Time Changes&lt;/h4&gt;  &lt;p&gt;The message retention time has DECREASED from 15 days to 4 days. This is not a good thing.&lt;/p&gt;  &lt;h4&gt;Message Size Changes&lt;/h4&gt;  &lt;p&gt;The maximum message size has DECREASED from 256 KB to 8 KB for both Query and SOAP requests. Seriously? &lt;/p&gt;  &lt;h4&gt;Number of Messages Received&lt;/h4&gt;  &lt;p&gt;They've DECREASED the maximum number of messages you can receive in one request from 256 to 10. So now you have to make 25 requests (which cost money) to get what you could have got out of 1 request.&lt;/p&gt;  &lt;h4&gt;Conclusion&lt;/h4&gt;  &lt;p&gt;I've always had a problem with how SQS was priced. I had planned to use it for a service that uses high volume queues locally, but the pricing is just off the hook and didn't make any sense. I'm not sure if the new pricing will make that better or worse, but they've also decreased the functionality quite a bit. &lt;/p&gt;  &lt;p&gt;It almost sounds like they are trying to sunset this service. &lt;/p&gt;  &lt;p&gt;In any case, you have 180 days to switch to the new API folks, so get on it. For the Java folks out there, &lt;a href="http://code.google.com/p/typica/"&gt;Typica&lt;/a&gt; is your best bet.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8917329674696551431-2515550040415863555?l=www.scalingout.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ScalingOut/~4/2s37VKoRMJ4" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.scalingout.com/feeds/2515550040415863555/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8917329674696551431&amp;postID=2515550040415863555" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/2515550040415863555?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/2515550040415863555?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ScalingOut/~3/2s37VKoRMJ4/amazon-drops-price-for-simple-queue.html" title="Amazon Drops the Price for Simple Queue Service (SQS), but there are some Caveats" /><author><name>Travis Reeder</name><uri>http://www.blogger.com/profile/01398330633165910535</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03697593268591053185" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total><feedburner:origLink>http://www.scalingout.com/2008/02/amazon-drops-price-for-simple-queue.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEMCRXY9eCp7ImA9WxZREEo.&quot;"><id>tag:blogger.com,1999:blog-8917329674696551431.post-6250766980770334387</id><published>2008-02-03T14:07:00.001-08:00</published><updated>2008-02-03T14:07:44.860-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-02-03T14:07:44.860-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="GigaSpaces" /><category scheme="http://www.blogger.com/atom/ns#" term="Architectures" /><category scheme="http://www.blogger.com/atom/ns#" term="Scaling" /><title>Why Tier Based Architectures Don't Scale</title><content type="html">&lt;p&gt;Nati Shalom from &lt;a href="http://www.gigaspaces.com"&gt;GigaSpaces&lt;/a&gt; wrote an interesting piece on his blog about why tier based architecture's don't scale. Think &amp;quot;weakest link&amp;quot; and your half way there. &lt;/p&gt;  &lt;p&gt;&lt;a href="http://natishalom.typepad.com/nati_shaloms_blog/2008/01/how-to-explain.html"&gt;Read it here&lt;/a&gt;.&lt;/p&gt;  &lt;p&gt;While it sounds like he has a good point, some real world examples would have been nice. &lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8917329674696551431-6250766980770334387?l=www.scalingout.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ScalingOut/~4/Q595-5LWamM" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.scalingout.com/feeds/6250766980770334387/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8917329674696551431&amp;postID=6250766980770334387" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/6250766980770334387?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/6250766980770334387?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ScalingOut/~3/Q595-5LWamM/why-tier-based-architectures-don-scale.html" title="Why Tier Based Architectures Don&amp;#39;t Scale" /><author><name>Travis Reeder</name><uri>http://www.blogger.com/profile/01398330633165910535</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03697593268591053185" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total><feedburner:origLink>http://www.scalingout.com/2008/02/why-tier-based-architectures-don-scale.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkYEQ3syfyp7ImA9WxZSFk4.&quot;"><id>tag:blogger.com,1999:blog-8917329674696551431.post-6854369303168996036</id><published>2008-01-29T11:15:00.001-08:00</published><updated>2008-01-29T11:15:02.597-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-01-29T11:15:02.597-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Database" /><category scheme="http://www.blogger.com/atom/ns#" term="Amazon" /><title>Another Cloud Database Coming Soon</title><content type="html">&lt;p&gt;&lt;a href="http://www.enterprisedb.com/"&gt;EnterpriseDB&lt;/a&gt; plans to release a cloud version of it's database offering which will run on Amazon EC2 and store it's data on S3. This will apparently compete directly with SimpleDB, but provide all the advanced relational database features we all know and love. &lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;In an interview conducted last week in advance of today's announcement of the Cloud Edition plans, Zurek declined to disclose specifics about the company's pricing plans. But the pricing &amp;quot;will be disruptive,&amp;quot; he said. &amp;quot;I don't think Oracle will like this.&amp;quot;&lt;/p&gt; &lt;/blockquote&gt;  &lt;p&gt;Sounds good to me. I'm not sure how these guys will package it up, but what I would really like to see is a simple on-demand model like SimpleDB with a real relational database. Create databases and tables on demand, pay only for storage and processing power, automatic/transparent scaling, no maintenance. &lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8917329674696551431-6854369303168996036?l=www.scalingout.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ScalingOut/~4/wA8wxeQYFQc" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.scalingout.com/feeds/6854369303168996036/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8917329674696551431&amp;postID=6854369303168996036" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/6854369303168996036?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/6854369303168996036?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ScalingOut/~3/wA8wxeQYFQc/another-cloud-database-coming-soon.html" title="Another Cloud Database Coming Soon" /><author><name>Travis Reeder</name><uri>http://www.blogger.com/profile/01398330633165910535</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03697593268591053185" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://www.scalingout.com/2008/01/another-cloud-database-coming-soon.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CEMGSHgyfyp7ImA9WxZSEkU.&quot;"><id>tag:blogger.com,1999:blog-8917329674696551431.post-1677738805730778150</id><published>2008-01-25T09:33:00.001-08:00</published><updated>2008-01-25T09:33:49.697-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-01-25T09:33:49.697-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Java" /><category scheme="http://www.blogger.com/atom/ns#" term="Ruby" /><category scheme="http://www.blogger.com/atom/ns#" term="Programming Languages" /><category scheme="http://www.blogger.com/atom/ns#" term="JVM" /><title>Java has Achieved Cockroach Status</title><content type="html">&lt;p&gt;I just read through &lt;a href="http://blogs.tedneward.com/2008/01/15/Java+QuotDonequot+Like+The+Patriots+Or+QuotDonequot+Like+The+Dolphins.aspx" target="_blank"&gt;this article on Ted Neward's blog&lt;/a&gt; where he attempts to answer this question. He makes a good point about how prolific the JVM really is today. &lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;Here's a thought: Let's leave Java where it is, and just start creating new JVM languages that cater to specific needs. You can call them Java, too, if you like. Or something else, like Scala or Clojure or Groovy or JRuby or CJ or whatever suits your fancy. &lt;strong&gt;&lt;font color="#0080ff"&gt;Since everybody compiles down to JVM bytecode, it's all really academic--they're &lt;em&gt;all&lt;/em&gt; Java, in some fundamental way&lt;/font&gt;&lt;/strong&gt;. Which means that Java can thus rest easy, knowing that it fought the good fight, and that others equally capable are carrying on the tradition of JVM programming.&lt;/p&gt; &lt;/blockquote&gt;  &lt;p&gt;Beyond that, I'll add that it's also found everywhere: computers, phones, and all sorts of other devices.&lt;/p&gt;  &lt;p&gt;&lt;a href="http://www.pluralsight.com/blogs/dbox/archive/2008/01/15/49926.aspx" target="_blank"&gt;Don Box from Microsoft responded to the article on his blog&lt;/a&gt; saying:&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;Java has achieved cockroach status and its inventors should be proud.&lt;/p&gt;    &lt;p&gt;Mission accomplished.&lt;/p&gt; &lt;/blockquote&gt;  &lt;p&gt;All I can say is that I'm glad I'm on the cockroach team.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8917329674696551431-1677738805730778150?l=www.scalingout.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ScalingOut/~4/JRzetrG5MPs" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.scalingout.com/feeds/1677738805730778150/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8917329674696551431&amp;postID=1677738805730778150" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/1677738805730778150?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/1677738805730778150?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ScalingOut/~3/JRzetrG5MPs/java-has-achieved-cockroach-status.html" title="Java has Achieved Cockroach Status" /><author><name>Travis Reeder</name><uri>http://www.blogger.com/profile/01398330633165910535</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03697593268591053185" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://www.scalingout.com/2008/01/java-has-achieved-cockroach-status.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkMMRXwyeCp7ImA9WxZTFkU.&quot;"><id>tag:blogger.com,1999:blog-8917329674696551431.post-5611429797677465867</id><published>2008-01-18T10:21:00.001-08:00</published><updated>2008-01-18T10:21:24.290-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-01-18T10:21:24.290-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Twitter" /><category scheme="http://www.blogger.com/atom/ns#" term="EC2" /><title>EC2 Teaches Bad Habits</title><content type="html">&lt;p&gt;A &lt;a href="http://explore.twitter.com/esh/statuses/554513932" target="_blank"&gt;twitter from Eric Hammond&lt;/a&gt;:&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;EC2 teaches bad habits: I almost shutdown a remote non-EC2 server when I was done using it&lt;/p&gt;&lt;/blockquote&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8917329674696551431-5611429797677465867?l=www.scalingout.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ScalingOut/~4/5UdY__TfqOU" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.scalingout.com/feeds/5611429797677465867/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8917329674696551431&amp;postID=5611429797677465867" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/5611429797677465867?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/5611429797677465867?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ScalingOut/~3/5UdY__TfqOU/ec2-teaches-bad-habits.html" title="EC2 Teaches Bad Habits" /><author><name>Travis Reeder</name><uri>http://www.blogger.com/profile/01398330633165910535</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03697593268591053185" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://www.scalingout.com/2008/01/ec2-teaches-bad-habits.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUMNQng-cSp7ImA9WB9UGE4.&quot;"><id>tag:blogger.com,1999:blog-8917329674696551431.post-6230879235229191938</id><published>2007-12-16T11:21:00.001-08:00</published><updated>2007-12-16T12:38:13.659-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-12-16T12:38:13.659-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="SimpleDB" /><category scheme="http://www.blogger.com/atom/ns#" term="BigTable" /><category scheme="http://www.blogger.com/atom/ns#" term="Google" /><category scheme="http://www.blogger.com/atom/ns#" term="Amazon" /><title>Why SimpleDB Matters</title><content type="html">&lt;p&gt;Here's &lt;a href="http://pierrebsas.blogspot.com/2007/12/amazon-simpledb-101-why-it-matters.html"&gt;a good post on SimpleDB usages and why SimpleDB matters&lt;/a&gt;.&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;Very, very simplistically speaking, domains are like tables, with items like rows and attributes like columns. A query cannot cross domains, so in this analogy you can&amp;#8217;t &amp;#8220;join&amp;#8221; domains. But that sort of thinking is a holdover from the relational database normalized model.In reality a domain is much more like a database, so we have to stop thinking in terms of tables and joins.&lt;/p&gt; &lt;/blockquote&gt;  &lt;p&gt;And another interesting post:&lt;/p&gt;  &lt;p&gt;&lt;a href="http://smoothspan.wordpress.com/2007/12/15/to-rule-the-clouds-takes-software-why-amazon-simpledb-is-a-huge-next-step/"&gt;To Rule the Clouds Takes Software: Why Amazon SimpleDB is a Huge Next Step&lt;/a&gt;&lt;/p&gt;  &lt;p&gt;I love how this one starts with a good Lord of the Rings analogy:&lt;/p&gt;  &lt;p align="center"&gt;&lt;em&gt;One Ring to rule them all, One Ring to find them,     &lt;br /&gt;One Ring to bring them all and in the darkness bind them&amp;#8230;&lt;/em&gt;&lt;/p&gt;  &lt;p align="center"&gt;&lt;a href="http://en.wikipedia.org/wiki/J._R._R._Tolkien"&gt;J. R. R. Tolkien&lt;/a&gt;&lt;/p&gt;  &lt;p align="left"&gt;Amazon is handing out the nine rings to us humans, that's for sure, but I don't think they are as evil as Sauron... or are they? ;) &lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8917329674696551431-6230879235229191938?l=www.scalingout.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ScalingOut/~4/C7PNQxT1A-o" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.scalingout.com/feeds/6230879235229191938/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8917329674696551431&amp;postID=6230879235229191938" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/6230879235229191938?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/6230879235229191938?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ScalingOut/~3/C7PNQxT1A-o/why-simpledb-matters.html" title="Why SimpleDB Matters" /><author><name>Travis Reeder</name><uri>http://www.blogger.com/profile/01398330633165910535</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03697593268591053185" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://www.scalingout.com/2007/12/why-simpledb-matters.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkYERXg6fCp7ImA9WB9UFkU.&quot;"><id>tag:blogger.com,1999:blog-8917329674696551431.post-4429061048705703550</id><published>2007-12-14T16:55:00.001-08:00</published><updated>2007-12-14T16:55:04.614-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-12-14T16:55:04.614-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="SimpleDB" /><category scheme="http://www.blogger.com/atom/ns#" term="S3" /><category scheme="http://www.blogger.com/atom/ns#" term="Database" /><category scheme="http://www.blogger.com/atom/ns#" term="Amazon" /><category scheme="http://www.blogger.com/atom/ns#" term="EC2" /><title>Amazon Rolls Out The Missing Piece to Its Web Services Empire: SimpleDB</title><content type="html">&lt;p&gt;Amazon announced a limited beta for &lt;a href="http://www.amazon.com/b/ref=sc_fe_c_1_3435361_1?ie=UTF8&amp;amp;node=342335011&amp;amp;no=3435361&amp;amp;me=A36L942TSJ2AJA"&gt;SimpleDB&lt;/a&gt;, their latest web service offering. A reliable, scalable database has been a particular pain point for EC2 users since EC2 is unreliable. Running a database on an EC2 instance is like driving your car over the Bay Bridge; you just know it's going to fall down at some point, you just hope you're not driving that day (and that your parachute (backup) is freshly packed). &lt;/p&gt;  &lt;p&gt;To use Amazon SimpleDB you:&lt;/p&gt;  &lt;ul&gt;   &lt;li&gt;CREATE a new &lt;i&gt;domain&lt;/i&gt; to house your unique set of structured data.&lt;/li&gt;    &lt;li&gt;GET, PUT or DELETE &lt;i&gt;items&lt;/i&gt; in your domain, along with the attribute-value pairs that you associate with each item.&amp;#160; Amazon SimpleDB automatically indexes data as it is added to your domain so that it can be quickly retrieved; there is no need to pre-define a schema or change a schema if new data is added later.&amp;#160; Each item can have up to 256 attribute values.&amp;#160; Each attribute value can range from 1 to 1,024 bytes.&lt;/li&gt;    &lt;li&gt;QUERY your data set using this simple set of operators: =, !=, &amp;lt;, &amp;gt; &amp;lt;=, &amp;gt;=, STARTS-WITH,&amp;#160; AND, OR, NOT, INTERSECTION AND UNION.&amp;#160; Query execution time is currently limited to 5 seconds.&amp;#160; Amazon SimpleDB is designed for real-time applications and is optimized for those use cases. &lt;/li&gt;    &lt;li&gt;Pay only for the resources that you consume.&lt;/li&gt; &lt;/ul&gt;  &lt;p&gt;Some key points:&lt;/p&gt;  &lt;ul&gt;   &lt;li&gt;&lt;b&gt;Scalable&lt;/b&gt;      &lt;br /&gt;Amazon SimpleDB allows you to easily scale your application.&amp;#160; You can quickly create new domains as your data grows or your request throughput increases.&amp;#160; For the Beta release, a single domain is limited in size to 10 GB and you are limited to a maximum of 100 domains; however, over time these limits may be raised.&lt;/li&gt;    &lt;li&gt;&lt;b&gt;Fast&lt;/b&gt;      &lt;br /&gt;Amazon SimpleDB provides quick, efficient storage and retrieval of your data to support high performance web applications.&lt;/li&gt;    &lt;li&gt;&lt;b&gt;Reliable&lt;/b&gt;      &lt;br /&gt;The service runs within Amazon's high-availability data centers to provide strong and consistent performance.&amp;#160; To prevent data from being lost or becoming unavailable, your fully indexed data is stored redundantly across multiple servers and data centers.&lt;/li&gt; &lt;/ul&gt;  &lt;p&gt;How many smart people does Amazon have working on this stuff?&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8917329674696551431-4429061048705703550?l=www.scalingout.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ScalingOut/~4/PaGU-YwW6jw" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.scalingout.com/feeds/4429061048705703550/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8917329674696551431&amp;postID=4429061048705703550" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/4429061048705703550?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/4429061048705703550?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ScalingOut/~3/PaGU-YwW6jw/amazon-rolls-out-missing-piece-to-its.html" title="Amazon Rolls Out The Missing Piece to Its Web Services Empire: SimpleDB" /><author><name>Travis Reeder</name><uri>http://www.blogger.com/profile/01398330633165910535</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03697593268591053185" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://www.scalingout.com/2007/12/amazon-rolls-out-missing-piece-to-its.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0YBQns9eip7ImA9WB9UEU4.&quot;"><id>tag:blogger.com,1999:blog-8917329674696551431.post-5477222293205114995</id><published>2007-12-08T10:33:00.001-08:00</published><updated>2007-12-08T10:39:13.562-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-12-08T10:39:13.562-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="S3" /><category scheme="http://www.blogger.com/atom/ns#" term="Ooyala" /><category scheme="http://www.blogger.com/atom/ns#" term="Start-Up Challenge" /><category scheme="http://www.blogger.com/atom/ns#" term="Funding" /><category scheme="http://www.blogger.com/atom/ns#" term="Amazon" /><category scheme="http://www.blogger.com/atom/ns#" term="EC2" /><title>Amazon Announces $100,000 Start-Up Challenge Winner</title><content type="html">&lt;p&gt;&lt;a href="http://www.ooyala.com/"&gt;&lt;img src="http://www.ooyala.com/cacheable/2262/www/images/headerlogo_company.gif" align="right" /&gt;&lt;/a&gt; Out of over 900 business plan entries submitted by developers building their products and services using the AWS platform, &lt;strong&gt;&lt;a href="http://www.ooyala.com/"&gt;Ooyala&lt;/a&gt;&lt;/strong&gt; is announced the winner of the Amazon Web Services Start-Up Challenge. Ooyala is a video company delivering a high quality interactive video experience with monetization and analytics tools for video publishers and advertisers. As the grand prize winner, Ooyala will receive $50,000 in cash, $50,000 in Amazon Web Service credits and an investment offer from Amazon.com. &lt;a href="http://www.amazon.com/b/ref=sc_fe_c_1_3435361_3?ie=UTF8&amp;amp;node=377634011&amp;amp;no=3435361&amp;amp;me=A36L942TSJ2AJA"&gt;Click here for more on the contest.&lt;/a&gt;&lt;/p&gt;  &lt;p&gt;Ooyala has built a platform to deliver video content for publishers and targeted advertising via an interactive video experience. Ooyala is built on Amazon Web Services including Amazon EC2, used for video and analytics processing, and Amazon S3 for content storage and delivery. Ooyala leverages Amazon FPS to process both content and ad serving payments. Amazon Mechanical Turk and Amazon SQS are also utilized by Ooyala. &lt;/p&gt;  &lt;p&gt;&amp;#8220;When we started Ooyala, we were warned that we would spend most of our time in datacenters at 2 a.m. making sure everything worked,&amp;#8221; said Sean Knapp, Founder and President of Technology for Ooyala. &amp;#8220;Very few companies in the world can provide the infrastructure services Amazon can provide. Why would you do it yourself? AWS has enabled Ooyala to build, deploy and scale our product in record time, raising the bar for rapid innovation.&amp;#8221;&lt;/p&gt;  &lt;p&gt;&lt;a href="http://www.businesswire.com/portal/site/home/index.jsp?epi%2dcontent=NEWS%5fVIEW%5fPOPUP%5fTYPE&amp;amp;newsId=20071206006270&amp;amp;ndmHsc=v2%2aA1196946000000%2aB1197040954000%2aDgroupByDate%2aJ2%2aN1000837&amp;amp;newsLang=en&amp;amp;beanID=202776713&amp;amp;viewID=news%5fview%5fpopup"&gt;Read more at Business Wire&lt;/a&gt;.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8917329674696551431-5477222293205114995?l=www.scalingout.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ScalingOut/~4/9KInLYAyZiU" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.scalingout.com/feeds/5477222293205114995/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8917329674696551431&amp;postID=5477222293205114995" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/5477222293205114995?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/5477222293205114995?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ScalingOut/~3/9KInLYAyZiU/amazon-announces-100000-start-up.html" title="Amazon Announces $100,000 Start-Up Challenge Winner" /><author><name>Travis Reeder</name><uri>http://www.blogger.com/profile/01398330633165910535</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03697593268591053185" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://www.scalingout.com/2007/12/amazon-announces-100000-start-up.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEcARHo-eip7ImA9WB9WEEo.&quot;"><id>tag:blogger.com,1999:blog-8917329674696551431.post-4971456170687425874</id><published>2007-11-14T13:34:00.001-08:00</published><updated>2007-11-14T13:34:05.452-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-11-14T13:34:05.452-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Paid AMI" /><category scheme="http://www.blogger.com/atom/ns#" term="Linux" /><category scheme="http://www.blogger.com/atom/ns#" term="Redhat" /><category scheme="http://www.blogger.com/atom/ns#" term="Amazon" /><category scheme="http://www.blogger.com/atom/ns#" term="EC2" /><title>Redhat Living in the Clouds</title><content type="html">&lt;p&gt;&lt;img id="id" src="http://www.redhat.com/g/chrome/logo_rh_home.png" align="right" /&gt; The Amazon Elastic Compute Clouds that is. Redhat announced the availability of &lt;a href="http://www.redhat.com/solutions/cloud/"&gt;Redhat Enterprise on EC2&lt;/a&gt;, so now you can get Redhat Enterprise benefits but pay for it on demand.&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;Available at a starting price of $19/month per customer plus $0.21 per hour for every deployed server, plus additional bandwidth and storage fees.&lt;/p&gt; &lt;/blockquote&gt;  &lt;p&gt;From the sounds of it, it looks like they've just packaged RHEL up as a &lt;a href="http://developer.amazonwebservices.com/connect/entry.jspa?externalID=866"&gt;paid AMI&lt;/a&gt; so it'll be as easy as launching any old instance. Not a bad idea for enterprise Linux customers. &lt;/p&gt; &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8917329674696551431-4971456170687425874?l=www.scalingout.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ScalingOut/~4/qDQk8K1_EKg" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.scalingout.com/feeds/4971456170687425874/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8917329674696551431&amp;postID=4971456170687425874" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/4971456170687425874?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/4971456170687425874?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ScalingOut/~3/qDQk8K1_EKg/redhat-living-in-clouds.html" title="Redhat Living in the Clouds" /><author><name>Travis Reeder</name><uri>http://www.blogger.com/profile/01398330633165910535</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03697593268591053185" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://www.scalingout.com/2007/11/redhat-living-in-clouds.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEcBQX89fyp7ImA9WB9XGUo.&quot;"><id>tag:blogger.com,1999:blog-8917329674696551431.post-5855373608746212430</id><published>2007-11-13T09:47:00.001-08:00</published><updated>2007-11-13T09:47:30.167-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-11-13T09:47:30.167-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Facebook" /><category scheme="http://www.blogger.com/atom/ns#" term="Availability" /><category scheme="http://www.blogger.com/atom/ns#" term="Monitoring" /><title>The Perfect Excuse to use Facebook at Work: Server Monitor for Facebook</title><content type="html">&lt;p&gt;&lt;a href="http://www.facebook.com/apps/application.php?id=6540206257"&gt;&lt;img id="id" src="http://aycu13.webshots.com/image/32732/2003314381869832566_rs.jpg" /&gt; &lt;/a&gt;&lt;/p&gt;  &lt;p&gt;Here's a great, &lt;a href="http://www.facebook.com/apps/application.php?id=6540206257"&gt;free tool to monitor your servers&lt;/a&gt; from within &lt;a href="http://www.facebook.com"&gt;Facebook&lt;/a&gt;. This is the description on the app's about page:&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;Monitor your web servers in Facebook! Get a notification when your site goes down and when it comes back up. Show your server status on your profile too so your friends can see if you're a network admin rockstar or not.     &lt;br /&gt;&lt;b&gt;Features&lt;/b&gt;&lt;/p&gt;    &lt;ul&gt;     &lt;li&gt;Notifications via Facebook feed, email and SMS &lt;/li&gt;      &lt;li&gt;Checks every ten minutes &lt;/li&gt;      &lt;li&gt;10 second setup &lt;/li&gt;      &lt;li&gt;FREE!&lt;/li&gt;   &lt;/ul&gt;&lt;/blockquote&gt; &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8917329674696551431-5855373608746212430?l=www.scalingout.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ScalingOut/~4/br1TIDtu074" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.scalingout.com/feeds/5855373608746212430/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8917329674696551431&amp;postID=5855373608746212430" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/5855373608746212430?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8917329674696551431/posts/default/5855373608746212430?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ScalingOut/~3/br1TIDtu074/perfect-excuse-to-use-facebook-at-work.html" title="The Perfect Excuse to use Facebook at Work: Server Monitor for Facebook" /><author><name>Travis Reeder</name><uri>http://www.blogger.com/profile/01398330633165910535</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03697593268591053185" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://www.scalingout.com/2007/11/perfect-excuse-to-use-facebook-at-work.html</feedburner:origLink></entry></feed>
