I wrote recently that the time may be right for AWS to launch its own PaaS offering, if only to preempt any competitive threat from other providers’ increasingly business-friendly PaaS offerings. The time is indeed right, now that Google has introduced App Engine for Business.

I wrote last week that the time may be right for Amazon Web Services to launch its own platform-as-a-service (PaaS) offering, if only to preempt any competitive threat from other providers’ increasingly business-friendly PaaS offerings. The time is indeed right, now that Google has introduced to the world App Engine for Business.

That’s because App Engine for Business further advances the value proposition for PaaS. PaaS offerings have been the epitome of cloud computing in terms of automation and abstraction, but they left something to be desired in terms of choice. With solutions like App Engine for Business, however, the idea of choice in PaaS offerings isn’t so laughable. Python or Java. BigTable or SQL. It’s not AWS (not that any PaaS offering really can be), but it’s a big step in the right direction. App Engine for Business is very competitive in terms of pricing and support, too.

Google is often is cited as a cloud computing leader, but until now had yet to deliver a truly legitimate option for computing in the cloud. Mindshare and a legit product make Google dangerous to cloud providers of all stripes, including AWS.

The integration of the Spring Framework in App Engine for Business is important because it means that customers have the option of easily porting Java applications to a variety of alternative cloud environments. Yes, AWS supports Spring, but the point is that Google is now on board with what is fast becoming the de facto Java framework for both internal and external cloud environments.

Meanwhile, in the IaaS market, AWS is busy trying to distinguish itself on the services and capabilities levels now that bare VMs are becoming commodities. Thus, we get what we saw this week, with AWS cutting storage costs for customers who don’t require high durability (a move some suggest was in response to a leak about Google’s storage announcement), and increasing RDS availability with cross-Availability-Zone database architectures. It’s all about differentiation around capabilities, support and services, and every IaaS provider is engaged in this one-upmanship.

If PaaS is destined to become the preferred cloud computing model, and if the IaaS market is becoming a rat race of sorts, why not free cloud revenues from the IaaS shackles and the threat of PaaS invasion? Amazon CTO Werner Vogels will be among several cloud computing executives speaking at Structure 2010 June 23 & 24, so we should get a sense then what demands are driving future advances for AWS and other cloud providers. For more on Google vs. Amazon and PaaS vs. IaaS, read my entire post here.

You’re subscribed! If you like, you can update your settings

  1. Paul Washington Sunday, May 23, 2010

    I think this article is somewhat of an over dramatization of Google’s “threat” to AWS. Not everyone in “enterprise” wants to be pigeon holed into using Java (or Python). There are going to be quite a few use cases whereby legacy enterprise, in order to be wooed to the cloud, is going to want to take their legacy and working investments with them (hence if they’ve got apps they’ve already invested into and are maintaining written in C, C++, .NET, C#, VB, Ruby, etc. what motivation is there to spend the time moving to Java). Why does Google over rate Java (which is now in the hands of Larry Ellison’s Oracle)?

    1. Sun might be owned by Oracle, but Java is still quite open…

      I develop on a Sun based JDK, deploy it on a IBM JVM, this is why Java is powerful.

    2. It’s not just Java that’s the threat, but the .NET and Ruby PaaS options, too. The point with Google is that it has the monetary means and the mindshare to be a real threat on the Java and Python fronts. It can roll out new services and play the pricing game like many AWS competitors cannot.

  2. Impulse Magazine Sunday, May 23, 2010

    I don’t think that Amazon should worry too much because they make Google a lot of money

  3. App Engine + Google Voice = Super-charged Communication Platform Sunday, June 27, 2010

    [...] By Brian McConnell Jun. 27, 2010, 7:00am PDT No Comments       App Engine, a powerful and easy-to-use cloud-based development environment, definitely has its issues, among [...]

  4. AppliGate site in de cloud? « AppliGate Consultancy Friday, August 27, 2010

    [...] Why Amazon Should Worry About Google App Engine for Business (gigaom.com) [...]

  5. Which Java-PaaS Options Will Win Developers’ Hearts?: Cloud « Sunday, December 5, 2010

    [...] Another question is whether supporting only a single framework — like VMware partners Google and Saleforce.com do with Spring — is the best idea when trying to build a large developer base. [...]

  6. Is AWS Targeting Netflix With 5TB Objects?: Cloud « Friday, December 10, 2010

    [...] its eyes set on winning bigger customers with bigger computing needs. I’ve said in the past that AWS needs a PaaS offering, but I’m beginning to question just how much it does. It doesn’t need to rely on developers [...]

Comments have been disabled for this post