7 Comments

Summary:

When Google first released App Engine as a “Preview Release” last April, developers had relatively little computing power. Only a few apps got Google’s permission to grow beyond the free computing quotas, including BuddyPoke, Lingospot, Mentalfloss and Giftag.com. Now, the company’s going to start charging for […]

When Google first released App Engine as a “Preview Release” last April, developers had relatively little computing power. Only a few apps got Google’s permission to grow beyond the free computing quotas, including BuddyPoke, Lingospot, Mentalfloss and Giftag.com. Now, the company’s going to start charging for its App Engine cloud platform. That’s welcome news for early adopters of the cloud computing platform, because even if they have to pay, they’ll now have access to the company’s vast computing resources.

Since the launch of App Engine, Google’s been collecting feedback from developers. It’s added SSL support, a status dashboard, and a memcache API, and is working on other features, such as a task queue and additional programming languages.

Google’s taken a lot of flak over the question of cloud lock-in, and Pete Koomen, the Product Manager for App Engine, says the company is trying to be as open as possible. “We want to encourage openness,” said Koomen, pointing out that there are no special hooks between App Engine and other Google services. “The more proprietary the APIs, the easier it is for developers to lock themselves in,” he said.

Making App Engine a paid service is another step toward establishing the developer ecosystem we described in December. While Google wouldn’t confirm our suspicions, Koomen did point out that it’s possible to write an App Engine application restricted to only those within your own domain. If that ecosystem prediction comes true, Google will have a platform for writing, running, and selling software to millions of Google Apps users. Think AppExchange for small and medium-sized businesses.

Here are the details on the new pricing for developers who go beyond their free quotas:

  • $0.10 per CPU core hour of computing
  • $0.10 per GB of inbound traffic and $0.12 per GB of outbound traffic
  • $0.15 per GB of data stored by the application
  • $0.0001 per email sent by the application

Google will continue to offer free accounts, although their capacity will be reduced from where it is today. Koomen said the goal is to make a “well-written” web application — that handles about 5 million page views a month — free, and for developers to pay beyond this amount.

  1. Any idea when the prices will go into effect? Didn’t see a link to the formal announcement in the post.

  2. Shion Deysarkar Tuesday, February 24, 2009

    Any idea how Google defines a CPU-Hr? I.e., is it a 2 GHz machine or what? The FAQ says it’s a megacycle, but that doesn’t really answer the question.

  3. @Shion

    I have the same question. Amazon’s EC2 charges for an active cpu. Its either “on” or “off”, regardless of how much work that CPU is doing. My impression from the Google AppEngine was that the pricing would be based on cpu cycles expended through handling work/traffic. So, you could consume fractions of physical CPU’s, and thus not have to start with the $80/month that EC2 demands for a CPU. I would appreciate an explanation.

  4. Thanks for the questions — I’ve asked the guys at Google to chime in and clarify here.

  5. Great questions. Our mechanism for metering CPU usage is outlined here:

    http://code.google.com/appengine/docs/quotas.html#Requests

    Essentially, we use a generic 1.2 GHz Intel x86 processor as a reference when calculating an app’s usage. An app uses CPU to handle requests (in the Python layer) and also when interacting with the datastore. The actual amount used by an app to handle a given request is highly dependent on what the app actually does. Apps that do a lot of heave datastore writing and Python-layer processing will use more CPU, while apps that make extensive use of our Memcache API and write sparingly will use less CPU.

    I hope this is helpful!

  6. Google Aims to Woo the Enterprise With Its Cloud Sunday, May 3, 2009

    [...] and didn’t allow users to consume of a lot of resources without permission. Google started charging developers to use App Engine three months ago, and earlier this month added to it support for Java, a programming language [...]

  7. Google Aims to Woo the Enterprise With Its Cloud [GigaOM] | BYOHosting.com Blogs Monday, May 4, 2009

    [...] and didn’t allow users to consume of a lot of resources without permission. Google started charging developers to use App Engine three months ago, and earlier this month added to it support for Java, a programming language [...]

Comments have been disabled for this post