At Google I/O this year, we announced that App Engine will be going out of preview before the end of the year.  One aspect of leaving preview is our new pricing model.  As promised we have started providing the ability for any application Admin to compare their existing cost to their new costs in the Admin Console (under “Billing History”).  Now that you have an idea of what changes may impact your app, we’ve also written an article to help you optimize your application.  We know many of you would rather code than think about your budget and billing settings, so to help with the transition we are extending a one-time courtesy credit of $50 to all free Apps that sign up for billing and all paid Apps that modify their budgets between now and October 31, 2011.  Once you have signed up or made changes to your billing settings, a $50 credit will appear in the “Billing History” area of the Admin Console for your application. For more information on how to enable billing or change your settings, please see Billing and Budgeting Resources.





This is a big step for the App Engine Team; thank you for your continued support and feedback, and we hope you find these tools useful as we get closer to our goal of leaving preview!




Posted by the App Engine Team

We’re pleased to announce another App Engine release today. You might have noticed that the rate of releases has gone up slightly in the past few months. We’ve made some changes internally so we are looking to push out a new release every month. This month includes a few Datastore updates, some changes to Blobstore API and Memcache API, and finally a new feature for Java developers.
We’re pleased to announce another App Engine release today. You might have noticed that the rate of releases has gone up slightly in the past few months. We’ve made some changes internally so we are looking to push out a new release every month. This month includes a few Datastore updates, some changes to Blobstore API and Memcache API, and finally a new feature for Java developers.



Python and Java Changes



  • Blobstore API - We’ve removed the limits on the size of blob uploads. You can now upload files of any size, allowing your app to serve images, video, or anything your internet connection can handle.


Datastore Changes



  • Index retrieval - We’ve added the ability for you to programmatically retrieve the list of indexes you’ve currently defined in the datastore, as well as their statuses.

  • Datastore Admin - You can now enable the Datastore Admin function from the Admin Console. This will allow Java users to make use of this functionality, like deleting all entities of a certain kind, without having to upload a Python version of their application. And for Python developers, you no longer need to enable this in your app.yaml file.

  • HRD Migration Trusted Testers - We are seeking early adopters to try out an improved HRD migration tool that requires a read-only period relative to your datastore write rate (as opposed to your datastore size, which is how the current version behaves). Please see the release notes for more information.


Python Updates


  • Memcache API - We now support the CAS (compare-and-swap) operation in our Python Memcache API (Java already had it). This can be used to update a value in Memcache only if no other requests have updated it between when the value was retrieved and when you go to update it.


Java Updates



    • Download app - Using the AppCfg download_app command, you can download any files that were uploaded from your war directory when you last updated the app version.


    This release also contains small updates and bugfixes for both Python and Java so be sure to check out the full release notes. Feedback, discussion, and questions can be posted in our Google Group.

    Posted by The App Engine Team

    As we get ready for App Engine to leave preview release later this year, we want to make clear that in addition to improving our reliability, adding new features, and introducing developer support, we are also committed to demonstrating we have sufficient controls in place to safeguard the data you store with us.

    As we get ready for App Engine to leave preview release later this year, we want to make clear that in addition to improving our reliability, adding new features, and introducing developer support, we are also committed to demonstrating we have sufficient controls in place to safeguard the data you store with us.


    Today we are happy to announce that over the past few weeks Google App Engine successfully completed the audit process for the SAS70 Type II, SSAE 16 Type II, and ISAE 3402 Type II standards.


    You can read more about the Google’s certifications and commitment to protect user data on the Enterprise blog.



    Posted by The App Engine Team