Comments on: PyOAE renamed DjOAE

By: Ian

Ian — Sun, 06 May 2012 10:40:50 +0000

I am using simplejson with custom encoders to produce the Json, manly because its quick and uses C code when it can. Those are wired in using standaard DJango views, nothing special. I thought about using Piston, but found simplejson, encoders and views simple and easy so I never got to trying it. I am generally not doing any error logging, so I use the standard logging API and when I have everything in an area working I remove all the routine logging so that all that appears in the log file is 1 line per request. That seems to be quite effective in avoiding loads of lines in the log files. I'll have a look at Sentry though it looks usefull, as does the Engineering blog at Instagram, where they run 100+ DJango instances on EC2 using a PostgreSQL + REDIS backend. Interestingly they have chosen Solr rather than Elastic Search for their search backend.

By: gaeremyncks

gaeremyncks — Sun, 06 May 2012 08:58:16 +0000

Is there any chance of making the repository public?

I’m currently working on a Django backed app and we’re using Piston for our CRUD-typed APIs. I’d be interested to see what you’re using? I have a feeling we might get away with just using plain Django views.

Did you have a look at Sentry for doing error logging? We’ve recently enabled this and it’s 10 times better than digging through enormous amount of log files.

By: Charles Severance

Charles Severance — Wed, 02 May 2012 04:21:45 +0000

This is cool because Django is the framework used by Google App Engine (with special Google tweaks). Since 2009, I have taught roughly 550 University of Michigan graduate students AppEngine and so they know wgsi, templates, models, etc. I chose App Engine/Django because I felt it was the single most complete and approachable full-stack web framework and we teach Python programming in the previous course. The students love it.

While I am not sure how may super-scalable apps run *on* the Google infrastructure, Google sure has made Django far more popular. I think lots of folks cut their teeth on App Engine for free (buying my awesome O’Reilly book) and then when they want to go large-scale – move to Django. My Appengine Book has a web site at http://www.appenginelearn.com and my Python book is at http://www.py4inf.com.