djangae

The built-in Django libraries for Django on App Engine are severely outdated. I have new guides that just vendor in recent version: https://cloud.google.com/python/django/appengine However there are a lot of tricky issues with Django on App Engine so I would also look into Djangae: https://github.com/potatolondon/djangae As far as Kubernetes, the OP and I had some independent discovery and started working on similar material at the same time. I also have some Django/Kubernetes content, both CloudSQL (MySQL) and Postgres in Kubernetes: https://cloud.google.com/python/django/container-engine (CloudSQL) https://medium.com/google-cloud/deploying-django-postgres-re... (Postgres) My biggest reason for running the database in Kubernetes is a) CloudSQL doesn't currently support Postgres and b) it's interesting. Seems like OP had similar motivatio

Agree, but there are tools to help. We maintain Djangae, to run Django on App Engine. https://github.com/potatolondon/djangae

Django works well on App Engine. If you are using CloudSQL you can use vanilla models, but if you are using the datastore then you can either choose not to use Django models at all (use ndb/db instead) or use django-nonrel or djangae which provide a db back-end. https://github.com/django-nonrel/djangoappengine https://github.com/potatolondon/djangae There's compromises in using the datastore - you can't do a lot of things that are dead simple with SQL, but in return you get massive scaleability. And the App Engine SDK itself can be a pain to work with, but there are also amazing features like task queues for background processing and Google Cloud Storage integration. Other than Django I've used Bottle for very small App Engine projects. Works great, it's faster than Django, I'd still prefer Django for a typical complex web app where you n