TechCrunch notices that:
Unlike Amazon Web Services’ loosely coupled architecture, which consists of several essentially independent services that can optionally be tied together by developers, Google’s architecture is more unified but less flexible. For example, it is possible with Amazon to use their storage service S3 independently of any other services, while with Google using their BigTable service will require writing and deploying a Python script to their app servers, one that creates a web-accessible interface to BigTable.
What this all means: Google App Engine is designed for developers who want to run their entire application stack, soup to nuts, on Google resources. Amazon, by contrast, offers more of an a la carte offering with which developers can pick and choose what resources they want to use.
This is the type of customer lock-in ( control point) that Google lacks in the search space. Strategically, very similar to what Salesforce.com is doing with its Force.com .
It appears that server-side business models, which originated in the Open Source revolution, are going to dominate computing during the next decade.
Google now has a shot at dominating two key application+service platforms: mobile( Android) and web utility ( App Engine).
No comments:
Post a Comment