4 ms·

I've used GAE quite extensively at my last place of work and really liked it overall. I experienced some large pain points when I was unable to use libraries th

I've used GAE quite extensively at my last place of work and really liked it overall. I experienced some large pain points when I was unable to use libraries that used C extensions, which I guess should be solvable now. The GAE runtime was (is?) also only available for Python 2.7. I wonder if there is a future possible migration path from the standard environment (Classical GAE) to the new flexible environment. For our product we also decided to use the Google NoSQL database Datastore. Since this is/was tightly integrated in the GAE Python runtime, with its own data model layer, it was an easy choice to implement. But, of course, made migration away from the Google Cloud really cumbersome. I guess you still are limited to use some of the Google Cloud Databases, but if you chose Cloud SQL maybe the migration is more feasible?

rdcastro 10y ago
We do have migration guides to the Flexible environment available per language. This is the link to the Python version: https://cloud.google.com/appengine/docs/flexible/python/migrating https://cloud.google.com/appengine/docs/flexible/python/migr... I hope that helps. A key tenet in the Flexible environment is portability. In the Datastore case, in particular, if you move to Cloud Datastore, that gives you portability across the Cloud Platform offerings or even if you want to run on premises or in a different Cloud provider.