AppEngine is to Amazon Web Services as HTTP is to SOAP.

Needless to say, I’m a fan.


no comment until now

  1. HTTP locks you into using only one vendor as your host/db?

  2. No, of course not. But Amazon has the same issue.

  3. Mark, I don’t get it either. What is your basis for that comparison? (I assume you mean to compare AppEngine to Amazon EC2 and S3. If not, then what?)

    I’m not knocking either, and am using Django at the moment so AppEngine looks nice. But it seems also to have more lockin than EC2 and S3.

  4. Ok, obviously a bit too obscure a comparison 8-)

    I mean that AWS – yes, EC2 specifically – seems built to accomodate many different kinds of systems, and so is optimized for no one in particular, just as SOAP is. Google App Engine, on the other hand, is optimized for one particular application, the Web, just as HTTP is.

  5. How about “Amazon Web Services is to AppEngine as HTTP is to SOAP” because App Engine allows interoperability with only one company (Google) and one language (Python), but AWS allows you to choose who you interoperate with, and which programming language(s) you work with because they expose the network protocol and data formats as their application interface?

    Or more likely, we’ll discover AppEngine supports the same kind of usage as AWS, if you write your own code to their interface. And Amazon will just release SDKs themselves that tie in some other Amazon services if you use their code…

    Ultimately, won’t this one just come down to price and convenience, rather than be a religious war?

Add your comment now