Author PhotoThis guest post was written by Massimiliano Pippi, Sr. Software Engineer, Evonove

Python developers have been using Django for a many years, most notably through django-nonrel, a fork of the original project that adds support for NoSQL databases. In 2012, Google App Engine 1.6.2 was released, with direct support for official Django releases and Google Cloud SQL.

Now that App Engine works with Django, you can deploy fairly complex web apps together with packages and middleware that use Django’s ORM. For example, with a little help from applications like Django Appengine Toolkit, which abstracts part of the Google Cloud configuration, you can deploy a fully functional blog in minutes.

These days there don’t seem to be many in the Django community taking advantage of App Engine integration, but I think it’s a good time for that to change. The brand new Cloud Console and the gCloud tool, new services like Cloud SQL and the efforts in supporting the Python SDK can make the life of a Djangonaut a lot easier on Google Cloud platform. We’re all looking forward to continued improvement in the client libraries and docs, but the current tools make it worthwhile to use right now. With a little code we can get very close to something like “one click deploy”.

See this post for details.


Massimiliano Pippi spends his day at work writing code, mostly Python, and experimenting with the whole stack of web applications, trying to stretch his skills in different directions. Open source fan and contributor, he is a passionate and active community member.

Posted by Scott Knaster, Editor