The Google App Engine SDK will let you run your web applications on Google's infrastructure. App Engine applications are easy to build, easy to maintain, and easy to scale as your traffic and data storage needs grow. With App Engine, there are no servers to maintain: You just upload your application, and it's ready to serve your users.
You can serve your app using a free domain name on the appspot.com domain, or use Google Apps to serve it from your own domain. You can share your application with the world, or limit access to members of your organization.
App Engine costs nothing to get started. Sign up for a free account, and you can develop and publish your application for the world to see, at no charge and with no obligation. A free account can use up to 500MB of persistent storage and enough CPU and bandwidth for about 5 million page views a month.
Here are some key features of "Google App Engine SDK":
· dynamic web serving, with full support for common web technologies
· persistent storage with queries, sorting and transactions
· automatic scaling and load balancing
· APIs for authenticating users and sending email using Google Accounts
· a fully featured local development environment that simulates Google App Engine on your computer
Requirements:
Limitations:
· Not only is creating an App Engine application easy, it's free! You can create an account and publish an application that people can use right away at no charge, and with no obligation. An application on a free account can use up to 500MB of storage and up to 5 million page views a month.
· During this preview period, only free accounts are available. In the near future, you will be able to purchase additional computing resources at competitive market prices. Free accounts will continue to be available after the preview period.
· During this preview period, you can register up to 3 applications.
· Application resource limits, or "quotas," are refreshed continuously. If your application reaches a time-based quota, such as bandwidth, the quota will begin refreshing immediately at the rate for the given limit. Fixed quotas such as storage use are only relieved when you decrease usage.
· Some features impose limits unrelated to quotas to protect the stability of the system. For example, when an application is called to serve a web request, it must issue a response within a few seconds. If the application takes too long, the process is terminated and the server returns an error code to the user. The request timeout is dynamic, and may be shortened if a request handler reaches its timeout frequently to conserve resources.
· Another example of a service limit is the number of results returned by a query. A query can return at most 1,000 results. Queries that would return more results only return the maximum. In this case, a request that performs such a query isn't likely to return a request before the timeout, but the limit is in place to conserve resources on the datastore.
· Attempts to subvert or abuse quotas, such as by operating applications on multiple accounts that work in tandem, are a violation of the Terms of Service, and could result in apps being disabled or accounts being closed.
What's New in This Release: [ read full changelog ]
All:
· A Datastore Admin fix in this release improves security by ensuring that scheduled backups can now only be started by a cron or task queue task. Administrators can still start a backup by going to the Datastore Admin in the Admin Console.
Python:
· Better support is now provided for the _$folder$ magic cloud storage keyword, and the implementation of basic mkdir()/rmdir() functionality via GCS streams.
· This release adds the wrappers @transactional_async and @transactonal_tasklet to correct (a) @transactional @tasklet being synchronous despite the decorator, and (b) @tasklet @transactional not running the generator in a transaction.
· Fixed a unicode issue associated with expressions in the Search API. A search with snippeted fields was failing on documents containing unicode characters.
· Fixed an issue with the dev_appserver not auto-detecting the lib/ directory in the SDK.
· Fixed an issue where Blobstore usage was being charged even though the actual data was being stored in Cloud S...
