I am going to begin a new django project with buddies. This project features a website, API to mobile programs, clearing and billing, internationalization aspects etc...

Do you know the benefits and drawbacks for implementing Google Application Engine versus. a normal website hosting solution?

Obviously GAE documentation praises their support for django, but I must listen to individuals with top notch experience.

Here is a general discussion regarding proscons for GAE. I am interested in the particulars regarding django (and related libraries) support.

What offered me on the internet Application Engine versus hosting a Django application were the next points:

  1. No DB Admin: We did not need to bother about giving and controlling a database. It was super productive for any two guy team.
  2. The Datastore Is Sensible: Considering the fact that we'd no RDBMS experience, the GAE Datastore just made lots of sense: It's a large hash table with transaction support. Certainly less complex -usage smart- than the usual traditional database.
  3. No Sysadmin Abilities Needed: Unsure in regards to you, but we didn't have mad sysadmin abilities. We simply authored an easy Python script that compressed our JavaScript and CSS and used. Which was adequate.
  4. Easy Deployment and Versioning: The internet interface enables you to try out a brand new version before which makes it the default. Therefore if the brand new version breaks, it is simple to roll for an older version.
  5. Easy Scalability: We enabled billing for approximately $4 each day, which gave us lots of CPU cycles along with a huge email quota. We did not need to bother about servers heading down. Again, this provide you with satisfaction if you are a little team.

Additionally you get quick access to cron, offline tasks and email. Oh, and you will also employ Django's templating engine, which is just one of my personal favorite items of Django.


  1. No FTP support: Lots of businesses still use FTP. You are able to only make HTTP/S requrests with GAE, which means you can't serve or upload FTP files.
  2. 3000 files per application: Your application cannot have in addition to that. As well as the Python version, you are able to bundle up extra libraries in zip files and employ zipserve for everyone them. It's my job to also sprite up small images into one and compress JavaScript and CSS and lump them into one file each.
  3. No costly information: All demands need to finish off in thirty seconds. But GAE provides you with Cron and task queues, so if you want to do super costly information, then you will need to break them up.
  4. Only pure Python libraries: Which means you can't use cPickle for instance.
  5. No legit image processing: They image processing API provides a subset of PIL, but when you must do heavy-lifting it is recommended to go outdoors (of GAE).

I'd recommend GAE for those who have a little team - which seems like you need to do, and you don't prefer to fool around with setting up servers. . .

All the best!

Its free quotas are very generous, which means you would not be having to pay anything until your site begins receiving a great deal of visits. Which causes it to be well suited for a project like yours, where you will possibly not know whether it will likely be successful.