Rowland Watkins

Exploring the use of Web and SOA technology in Hong Kong

Google App Engine vs. AWS

Posted by Rowland Watkins on 30 April, 2008 at 15:03

Is the Google App Engine a viable competitor to the current generation AWS?

To first approximation, I would argue no. As a Python (for the time being) web application platform, Google App Engine provides a highly scalable sandboxed environment that reduces what a developer can do with the underlying platform. In addition, the Google App Engine is a single Software as a Service (SaaS) platform. Developers and businesses cannot reuse distinct services for deploying OS images, storing data, creating complex business processes.

AWS on the other hand, is a low-level middleware infrastructure for developing new platforms. It provides primitive services for storage (S3), databases (SimpleDB), queuing (SQS), and computation (EC2) that enable high resilience and scalability. Consider Morph eXchange which offers Rails app hosting as a SaaS in a very similar fashion to the Google App Engine. And guess what, it actually runs on AWS! Unlike Google App Engine, however, Morph appears to allow businesses a free-er hand in their development decisions, permitting a full Ruby and Rails environment, together with managed access to S3.

The clear separation of duty in AWS is what gives it the edge over Google App Engine. EC2 allows businesses to deploy complete OS images from S3 to produce novel environments such as Morph. It gives business more control on how to put together business processes which currently isn’t possible with the Google App Engine.

Google App Engine is still in closed beta so it’s early days. It’s possible it will pick up and enable business to do things not possible in AWS. Then we would have competition and even more innovation at our finger tips.