It has been two weeks since Google’s unpopular pricing changes on its Google App Engine platform. The pricing left many developers upset since it pushed up their charges by 3x-5x in many cases. Google was pushed to the back foot in the face of the uproar and realized it needed to do a better job explaining the pricing and give developers a little more time to make changes in their apps.
At the AppEngine blog, the team has published a post that tackles the issue on 3 fronts: more time for developers to make changes to their apps, providing more quota and giving tips on how to reduce your application costs.
The main points to note are:
The blog post also contains information on various other ways to experiment until November 1 to see how to bring prices down. These include setting max idle instances and reserving instance hours which come at a lower cost. Developers are reminded again to go through the managing resources article published by the App Engine team.
The App Engine team is trying its best to be transparent in terms of how developers can work to reduce their costs further. It is clear that App Engine wants to provide a solid and reliable PaaS while continually providing new features. It is fair enough that there are costs involved to do that and the days of almost zero pricing are over. Developers will need to take a good look at their apps, make the changes that Google is recommending and see for themselves where the costs end up.
Peter Magnusson, Engineering Director responsible for Google App Engine has also penned his thoughts on App Engine Pricing.