canonical-ci-engineering team mailing list archive

[Nick Moffitt <nick@xxxxxxxxxxxxx>]

Andy Doan:
> On 12/03/2013 10:07 AM, Evan Dandrea wrote:
> > http://ubuntuone.com/0w12vBEgDVn4YUMh5JkoMq
> 
> Thinking about this generically, I'm not sure how specific these
> issues relate to Django. ie - all solutions at a minimum are going to
> require some sort of webserver and data-store and/or queue system. The
> specific solutions to make each implementation highly-available will
> differ, but they'll all require something.

I don't think anyone thinks these problems are unique to Django.  That's
why I used 'G' in the whiteboard scribble to stand in for "gunicorn", as
if to say, "here's an app server of some sort, IDK..."

The question of Django is of whether its entanglements come with enough
benefits to justify the cost.  The advantages of Django mostly come from
the heavy integration between its parts (mostly by way of the ORM, which
really betrays its 2005-era roots).  If all we're using is the WSGI
hooks and the URL routing, it seems like a good opportunity to advocate
for a switch to something that focuses on the same needs we have.

As I understand, Django was chosen partly because of support for
something that met a specific need that a project had at the time.
We're not really a heavily Django-driven shop, despite what the
Preferred Technology list says.

-- 
Nick Moffitt