<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Amazon EC2 &#8220;micro instances&#8221; vs. Google App Engine</title>
	<atom:link href="http://quoderat.megginson.com/2010/09/09/amazon-ec2-micro-instances-vs-google-app-engine/feed/" rel="self" type="application/rss+xml" />
	<link>http://quoderat.megginson.com/2010/09/09/amazon-ec2-micro-instances-vs-google-app-engine/</link>
	<description>Open information and technology.</description>
	<lastBuildDate>Thu, 16 Feb 2012 07:01:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Amazon EC2 Micro Instance Roundup &#171; Knowledge Networks</title>
		<link>http://quoderat.megginson.com/2010/09/09/amazon-ec2-micro-instances-vs-google-app-engine/#comment-3963</link>
		<dc:creator><![CDATA[Amazon EC2 Micro Instance Roundup &#171; Knowledge Networks]]></dc:creator>
		<pubDate>Tue, 15 Nov 2011 08:10:53 +0000</pubDate>
		<guid isPermaLink="false">http://quoderat.megginson.com/?p=393#comment-3963</guid>
		<description><![CDATA[[...] &#8220;Amazon EC2 &#8220;micro instances&#8221; vs. Google App Engine&#8220;: EC micro not necessarily cheaper than GAE, especially when considering additional costs for EBS storage. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] &#8220;Amazon EC2 &#8220;micro instances&#8221; vs. Google App Engine&#8220;: EC micro not necessarily cheaper than GAE, especially when considering additional costs for EBS storage. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Janess</title>
		<link>http://quoderat.megginson.com/2010/09/09/amazon-ec2-micro-instances-vs-google-app-engine/#comment-3917</link>
		<dc:creator><![CDATA[Janess]]></dc:creator>
		<pubDate>Fri, 19 Aug 2011 18:46:15 +0000</pubDate>
		<guid isPermaLink="false">http://quoderat.megginson.com/?p=393#comment-3917</guid>
		<description><![CDATA[Too many copmlmintes too little space, thanks!]]></description>
		<content:encoded><![CDATA[<p>Too many copmlmintes too little space, thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Akshay Arabolu</title>
		<link>http://quoderat.megginson.com/2010/09/09/amazon-ec2-micro-instances-vs-google-app-engine/#comment-3804</link>
		<dc:creator><![CDATA[Akshay Arabolu]]></dc:creator>
		<pubDate>Tue, 14 Jun 2011 18:54:35 +0000</pubDate>
		<guid isPermaLink="false">http://quoderat.megginson.com/?p=393#comment-3804</guid>
		<description><![CDATA[Hi David, 

Just came across this comparison of yours between Amazon EC2 vs Google App Engine. Great article. Wanted to know if you&#039;d like to feature it on getcomparisons.com? A project we’ve started to house all the best product comparisons on the web under one roof. You can back-link to this original article of course. Check it out, and if you&#039;re interested, I will send you an invite.

Cheers,
Akshay Arabolu, Founder]]></description>
		<content:encoded><![CDATA[<p>Hi David, </p>
<p>Just came across this comparison of yours between Amazon EC2 vs Google App Engine. Great article. Wanted to know if you&#8217;d like to feature it on getcomparisons.com? A project we’ve started to house all the best product comparisons on the web under one roof. You can back-link to this original article of course. Check it out, and if you&#8217;re interested, I will send you an invite.</p>
<p>Cheers,<br />
Akshay Arabolu, Founder</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Johnson</title>
		<link>http://quoderat.megginson.com/2010/09/09/amazon-ec2-micro-instances-vs-google-app-engine/#comment-3455</link>
		<dc:creator><![CDATA[Nick Johnson]]></dc:creator>
		<pubDate>Fri, 10 Sep 2010 09:57:48 +0000</pubDate>
		<guid isPermaLink="false">http://quoderat.megginson.com/?p=393#comment-3455</guid>
		<description><![CDATA[My take (admittedly I&#039;m biased, since I&#039;m on the App Engine team): 
&lt;blockquote&gt;I suspect that for many users, the ability to just drop in an app without having to spend weeks messing around with JVM-limited language ports[...]&lt;/blockquote&gt;

One of App Engine&#039;s major advantage is that you don&#039;t have to spend weeks messing around with server configuration, replication, failover, backups, monitoring, and so forth - it&#039;s much more drop-in than a bare server offering can be.

I think, though, that most of the advantages of the new micro instances will be complementary to App Engine, not in competition. Two things spring immediately to mind:
1. Micro instances provide a perfect hosting platform for TyphoonAE, an independent implementation of the App Engine platform. Users wanting to move low traffic apps off App Engine can set up a micro instance running TyphoonAE, and avoid having to modify their code.
2. Micro instances also provide a perfect platform for doing &#039;offline work&#039; for App Engine apps at relatively low volumes. Suppose, for example, that your app generally fits well on App Engine, but you have a few things, such as image recognition or processing, or video transcoding, that require facilities not available on App Engine. A micro instance may be exactly what you need in the way of minimal, low-cost server resources to perform this batch work.]]></description>
		<content:encoded><![CDATA[<p>My take (admittedly I&#8217;m biased, since I&#8217;m on the App Engine team): </p>
<blockquote><p>I suspect that for many users, the ability to just drop in an app without having to spend weeks messing around with JVM-limited language ports[...]</p></blockquote>
<p>One of App Engine&#8217;s major advantage is that you don&#8217;t have to spend weeks messing around with server configuration, replication, failover, backups, monitoring, and so forth &#8211; it&#8217;s much more drop-in than a bare server offering can be.</p>
<p>I think, though, that most of the advantages of the new micro instances will be complementary to App Engine, not in competition. Two things spring immediately to mind:<br />
1. Micro instances provide a perfect hosting platform for TyphoonAE, an independent implementation of the App Engine platform. Users wanting to move low traffic apps off App Engine can set up a micro instance running TyphoonAE, and avoid having to modify their code.<br />
2. Micro instances also provide a perfect platform for doing &#8216;offline work&#8217; for App Engine apps at relatively low volumes. Suppose, for example, that your app generally fits well on App Engine, but you have a few things, such as image recognition or processing, or video transcoding, that require facilities not available on App Engine. A micro instance may be exactly what you need in the way of minimal, low-cost server resources to perform this batch work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Moved Site to Amazon Cloud Micro Instance &#124; Sean Esopenko</title>
		<link>http://quoderat.megginson.com/2010/09/09/amazon-ec2-micro-instances-vs-google-app-engine/#comment-3453</link>
		<dc:creator><![CDATA[Moved Site to Amazon Cloud Micro Instance &#124; Sean Esopenko]]></dc:creator>
		<pubDate>Thu, 09 Sep 2010 22:45:05 +0000</pubDate>
		<guid isPermaLink="false">http://quoderat.megginson.com/?p=393#comment-3453</guid>
		<description><![CDATA[[...] found a pretty good comparison of Amazon EC2 micro Vs. Google Apps at Quoderat.  I have some experience utilizing Amazon EC2 so it wasn&#8217;t difficult to jump in.  For [...]]]></description>
		<content:encoded><![CDATA[<p>[...] found a pretty good comparison of Amazon EC2 micro Vs. Google Apps at Quoderat.  I have some experience utilizing Amazon EC2 so it wasn&#8217;t difficult to jump in.  For [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: davidmegginson</title>
		<link>http://quoderat.megginson.com/2010/09/09/amazon-ec2-micro-instances-vs-google-app-engine/#comment-3452</link>
		<dc:creator><![CDATA[davidmegginson]]></dc:creator>
		<pubDate>Thu, 09 Sep 2010 18:02:59 +0000</pubDate>
		<guid isPermaLink="false">http://quoderat.megginson.com/?p=393#comment-3452</guid>
		<description><![CDATA[Great point, John.  1 GB would probably be more database storage than most small apps need, but I&#039;m not sure about traffic.]]></description>
		<content:encoded><![CDATA[<p>Great point, John.  1 GB would probably be more database storage than most small apps need, but I&#8217;m not sure about traffic.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Cowan</title>
		<link>http://quoderat.megginson.com/2010/09/09/amazon-ec2-micro-instances-vs-google-app-engine/#comment-3451</link>
		<dc:creator><![CDATA[John Cowan]]></dc:creator>
		<pubDate>Thu, 09 Sep 2010 17:56:19 +0000</pubDate>
		<guid isPermaLink="false">http://quoderat.megginson.com/?p=393#comment-3451</guid>
		<description><![CDATA[You also need to factor in the US$0.10 per GiB per month and the US$0.10 per million I/O operations for Elastic Block Storage (replicated raw hard disks) if you want a drop-in replacement.  Amazon says a &quot;medium-sized web database&quot; with 100 GiB would probably cost another US$36 per month in EBS charges, so that&#039;s $50/month, plus S3 charges for backup (you can back up EBS disks to S3 in compressed form).  Still cheap and scalable, but not &lt;i&gt;quite&lt;/i&gt; as cheap as it sounded before.]]></description>
		<content:encoded><![CDATA[<p>You also need to factor in the US$0.10 per GiB per month and the US$0.10 per million I/O operations for Elastic Block Storage (replicated raw hard disks) if you want a drop-in replacement.  Amazon says a &#8220;medium-sized web database&#8221; with 100 GiB would probably cost another US$36 per month in EBS charges, so that&#8217;s $50/month, plus S3 charges for backup (you can back up EBS disks to S3 in compressed form).  Still cheap and scalable, but not <i>quite</i> as cheap as it sounded before.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

