Menu
I came across 2 different modules for porting Django to App Engine:
http://code.google.com/p/app-engine-patch/
http://code.google.com/p/google-app-engine-django/
Both seem to be compatible with Django 1.0,
The featured download of the latter is in Aug 08, whereas the former is Feb 09.
What are the relative merits?
What if I don't use the database at all, would it matter?
607
You can deploy a PostgreSQL or MySQL database that's managed and scaled by Google, and supported by Django. You can deploy Django with a Cloud Spanner backend using the python-spanner-django database backend.
Each Cloud Platform project can contain one App Engine application.
While App Engine supports many different services within a single application, Cloud Functions support individualized services. It's an important detail when comparing Google App Engine vs Cloud Functions. If your requirements don't include multiple services then Cloud Functions is a great choice.
At the moment, the App Engine Patch is outdated.
Djangoappengine and Django-Nonrel provide "Native Django on App Engine": http://www.allbuttonspressed.com/blog/django/2010/01/Native-Django-on-App-Engine
159
It's a bit late to answer, but the problem I've had so far with app-engine-patch is that, while it's a generally feature-complete port of Django 1.0, it discards Django models in favor of AppEngine's db.Model.
It's understandable, given the differences between the two, but it can require quite a bit of effort to port, depending on how involved your models (and usage of those models; this means you lose the Django query syntax as well).
26
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
