<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>#comments - Latest Comments in Google AppEngine &amp;#038; Amazon AWS</title><link>http://deasil.disqus.com/</link><description></description><atom:link href="https://deasil.disqus.com/google_appengine_038_amazon_aws/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Mon, 12 May 2008 07:40:59 -0000</lastBuildDate><item><title>Re: Google AppEngine &amp;#038; Amazon AWS</title><link>http://comments.deasil.com/2008/05/09/google-appengine-amazon-aws/#comment-449484</link><description>&lt;p&gt;That's a pretty interesting idea, I hope someone's working on it already. Another thing that would be most awesome is coming at the same idea from a different angle - if Amazon could just let EC2 instances grow arbitrarily gigantic, so you get one instance and it simply can use more and more compute cycles as necessary - or if it's a logistical effort, instead of adding more instances you add more "cpus" to a given instance. I suspect that would be workable for many but the top 1% of super cpu suckers like twitter - you'd end up with a massive instance but not mind bogglingly so.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">felix</dc:creator><pubDate>Mon, 12 May 2008 07:40:59 -0000</pubDate></item><item><title>Re: Google AppEngine &amp;#038; Amazon AWS</title><link>http://comments.deasil.com/2008/05/09/google-appengine-amazon-aws/#comment-447193</link><description>&lt;p&gt;RE: your virtual RackSpace idea, something like this may be a tool in the NOC:&lt;/p&gt;&lt;p&gt;&lt;a href="http://www.rightscale.com/" rel="nofollow noopener" target="_blank" title="http://www.rightscale.com/"&gt;http://www.rightscale.com/&lt;/a&gt;&lt;/p&gt;&lt;p&gt;I'm waiting for someone to move up to the next level of abstraction and effectively merge the appengine and AWS approaches. Something like a web framework based on [insert-favorite-framework-here] but with explicit supports for SimpleDB, SQS, S3, etc. as well as callbacks for notifying the master container about load conditions so that autonomous or rule-based VM instantiation (and reaping) can occur in response to traffic patterns.&lt;/p&gt;&lt;p&gt;A concept like that could be merged with a virtual hosting idea to give kinda the best of both worlds - flexibility and hands-offness...&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">mpodrazik</dc:creator><pubDate>Sun, 11 May 2008 19:52:09 -0000</pubDate></item></channel></rss>