[Answer]-What are some of the most appropriate ways for serving a large scale django app on Google Compute Engine?

1πŸ‘

βœ…

In order to have a fully scalable architecture, a good approach is to separate computation / serving, from file storage, and both from data storage. Going part by part:

  • file storage – Google Cloud Storage – by storing common service files in a GCS bucket, you get a central repository that is both highly-redundant, and scalable;

  • data storage – Google Cloud SQL – gives you a highly reliable, scalable MySQL-like database back-end, which can be resized at will to accommodate increasing database usage;

  • front-ends – GCE instance group – template-generated web / computation front-ends, setting up a resource pool into which a forwarding rule (load balancer) distributes incoming connections.

In a nutshell, this is one of the most adaptable set-ups I can think of, while you keep control over every aspect of the service and underlying infrastructure.

0πŸ‘

A simple approach would be to run a Python app on Google App Engine, which will auto-scale your instances (both up and down) and it supports Django, as mentioned by @spirulence in the comments.

Here are some starting points:

The last link shows which versions of Django are currently supported.

πŸ‘€Misha Brukman

Leave a comment