On Thu, Jan 21, 2010 at 8:58 AM, Luke Plant <l.plant...@cantab.net> wrote: > I would have guessed that a big issue with Django from an enterprise > perspective is its use of 'singletons'. [snip] > How much is this an issue in practice?
Other than databases, it hasn't been much of an issue with most of the BigCos I've been involved with. That's because... > One solution to this problem would be to have multiple Django > instances hosting different parts of your URL space, allowing them to > have multiple settings files. Bingo. All of the larger Django installations I've worked with haven't been just one project -- they've been dozens (hundreds in one case) of little bits, often cobbled together by different teams and sometimes different companies (in-house vs. contractors vs. off-the-shelf products). Django's URL/view decoupling looks *really* nice in these cases -- Django apps, properly written, don't care *where* in the URL space they live -- so this means that Django fits in well in these heterogenous environments. And I've yet to encounter a larger company that's anything but wildly heterogeneous. Peter's question below about enterprisy complexity and the dangers of becoming J2EE are good ones; I'm glad they're part of the discussion. It's difficult to know where to draw the line between simplicity and flexibility. Right now we have exactly 90 documented settings, some of which point at classes or interfaces that themselves have more complexity. To me this already sounds way too high, but it's nothing compared to the configuration options available in other environments -- PHP has about 600 php.ini settings! -- so there's obviously a matter of taste here. It's also important to keep in mind that part of the reason Django's had (some) success in corporate environments is *because* of the simplicity, not despite it. I've heard, over and over again, that teams that have switched to Django have done so at least in part because of the simplicity and ease-of-use. So we should be careful about setting up a false dichotomy where us hippie open source freaks only value simplicity and build toys and those square suit types who love FactoryManagerFactories because CIO magazine tells them to. The real world, as always, is a lot more complex. Jacob
-- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
