Django 1.7 on App Engine It could work! 

Massimiliano Pippi dev.pippi.im @maxpippi 

No content

No content

● 2008: App Engine dev preview release ● 2009: Django 1.0 added to the Python runtime ● 2011: django-nonrel ● [ … ] ● 2014: Cloud Sql GA release 

No content

pip install django -t /path/to/application/root # gae.pth /usr/local/google_appengine import dev_appserver; dev_appserver.fix_sys_path() import sys; sys.path.insert(1, ‘/path/to/application/root’) How? 

Why? 

Managed DB instances Cloud SQL ● fully managed: up and down scaling ● replication, patch management, backups ● no data lock-in ● MySql 5.5 and 5.6 available don’t be a jerk on MySql! 

Media storage Google Cloud Storage ● S3 fashioned file storage (versioning, CDN, ACLs, …) ● django media files (static files are smoothly handled by app engine by itself) ● no lock-in: implemented as a django custom file storage 

In-memory caching Memcache ● shared or dedicated instances ● monitoring tools come for free ● no lock-in: implemented as a django cache backend 

Asynchronous tasks Task Queue ● automatic scaling ● no more celery / python-rq ● workers hit http endpoints 

Push notifications Google Channel API ● provides js client via CDN ● easy to use ● not well suited if latency is key 

Authentication A non-feature of the Google Cloud Platform Getting rid of the Google Authentication system Use the more flexible Django contrib.auth framework instead 

External resources github.com/masci/django-appengine-toolkit ● no need to pip install -t ● memcache as cache backend ootb ● cloud storage as storage backend ootb ● database config from env vars 

Why not? Technology lock-in depending on the Google Cloud components in use Cloud SQL has no free tiers Python 2 only :( 

Thank you! dev.pippi.im @maxpippi