on discovery path

Google App Engine’s pricing: progress or throwback to pay-for-peak-usage?

Google App Engine is going to offer Adwords-style pricing - 
my first question was: if an additional 1000 people want to visit your website and as a result you go over the limit, what happens?

I found Google’s answer in one of the preview screenshots:

“As this budget represents the maximum you will be charged in one day, we recommend setting it higher than expected to buffer against sudden traffic surges.”

Translation: we turn those overflow visitors away.

Google may be thinking it can make more money with the Adwords model. SEO marketers know this very well.

As in the Adwords model where you don’t pay until impressions convert into clicks, I understand that you don’t pay until the storage/bandwidth/compute is consumed.

I also understand once you use up your budget limit in Adwords, your ads won’t compete in the auction for the rest of the day, resulting in a lost opportunity to advertise. That seems fair enough.

But what I don’t understand is how Google will tell users to willingly deny visitors each time they’re over-the-limit in App Engine. That goes against one of the key tenets of cloud computing: consumption-based pricing model.

One of the main reasons cloud computing ala Amazon AWS or Microsoft Azure is so attractive is because customers only pay for what they consume, eliminating the need to plan and purchase for peak usage.

It would be interesting to see how this plays out.  What’s next, an Adwords minimum bid-like requirement?

Related articles by Zemanta

• GigaOm: Google Opens Up App Engine Pricing Model (via Blog)
• Google Cloud Economics, The Quota