What is expected in the App Engine

1. Service for working with large files.
2. Support work with incoming mail
3. XMPP API.
4. Support for mapping datasets.
5. Cursors for database queries - overcoming the limit of 1000 entries.
6. Alert system (alerts) for exceptions in user applications.
7. Dump and restore storage system.

Source: App Engine Product Roadmap

1. Service for working with large files.
   When working with DataStore there is a limit on the size of the entity in 1 megabyte. One solution is to split the file into parts (units) and store them as separate entities. There is a separate library for such an operation - google-file-service , a description of which can also be found in recipes (cookbook) on the App Engine website. The library is not included in the standard set of App Engine libraries.
   Apparently Google is going to provide users with a similar library or introduce a new service that allows you to save large files without explicitly breaking it up into parts.
2. Support work with incoming mail
   App Engine has services that allow you to work with external resources only via the HTTP and HTTPS protocol, as well as send e-mail messages on behalf of users who have a Google account. What is meant by the service for working with incoming mail I have the following option: there will be a library with the functions of receiving messages from the mailboxes of users with Google accounts.
3. XMPP API
   By analogy with sending e-mail , there will be a library for sending XMPP messages using a Google account.
4. Support for mapping datasets
   I do not guess what is meant here. Maybe it means the data mapping from Datastore, for example in XML ? Or, maybe, some new types of connections between objects.
5. Cursors for database queries - overcoming the limit of 1000 entries.
   At the moment there is a limit on the number of records that can be returned when requesting a Datastore. To work with a large number of records, you will have to make more than one request to the Datastore.
   In this case, Google programmers are likely to introduce a new class that will act as a cursor in other databases . When iterating over the cursor when going beyond 1000 records, an implicit request will be made for the following records.
6. Alert system (alerts)
   A dump of all uncaught exceptions will be recorded and displayed in the administrative panel.
7. Dump and restore storage system
   It will be possible to dump the current state of the database, save it on the App Engine hosting and / or download to the local machine. The inverse recovery function from dump will also be available.

PS Thanks for the karma - moved the topic to the Google App Engine blog

Source: https://habr.com/ru/post/64165/