Hello Thomas,
By contrast to the standard environment, the Compute Engine environment would compare with a server you might simply run at home, in which case you have to provide what is automatically offered in the app engine standard environment. There is no scalability, so using one instance might prove not enough for your traffic. Your mentioned “decent uptime” depends on the envisaged traffic generated by your app, in that case. You are right about the CentOS; Google Compute Engine does not automatically update <https://cloud.google.com/compute/docs/images> the operating system or the software on your instances. There is a 99.95% guaranteed uptime in the SLA <https://cloud.google.com/compute/sla>. An excellent alternative would be the flexible environment <https://cloud.google.com/appengine/docs/flexible/java/flexible-for-standard-users>, that offers some services similar to the standard environment, especially important among these being scalability <https://cloud.google.com/appengine/docs/flexible/>. You are right, you can simply adapt <https://cloud.google.com/appengine/docs/flexible/python/migrating> your app to the Flexible Environment using Google Cloud Client libraries <https://cloud.google.com/apis/docs/cloud-client-libraries>. The same Cloud Datastore data is available regardless of if you use the App Engine libraries, the Google Cloud client libraries, or call the API directly, so, yes: you can still access your data in the Cloud Datastore. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/a4579fb2-5ccf-41df-af21-99c7698cefe4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
