On 9/30/07, Mark Green <[EMAIL PROTECTED]> wrote: > Hm, this raises some serious scalabity questions for me. > >From your description it sounds like there is no template > fragment caching, not even db connection pooling possible > with django?
You can cache anything you want to cache; read the caching documentation (the whole thing) before jumping to conclusions about that. At work we use a custom template Node class which caches its output, for example. As for database clustering, there's a philosophical issue here: Django shouldn't need to know whether there's one database server behind it, or five, or a hundred. We've had success using pgpool, for example, which -- from Django's point of view -- looks the same as any PostgreSQL database, but in reality is pooling connections and supports multiple actual databases running behind it. Think of it the same way you'd do load-balancing in front of your application: just as users shouldn't need to know that you have, say, ten web nodes running Django, and just as they shouldn't have to stop and ask, "which one of the site's web nodes to I want to request a page from?", Django shouldn't need to know how many database nodes you have, or which one it should talk to on each query. The less the various layers of your stack have to know about each other, the easier it'll be to make changes. I'd suggest reading the deployment chapter of the Django book for more details: http://www.djangobook.com/en/beta/chapter21/ > And what about integration with a messaging framework > (spread or somesuch) for efficient cluster communications? So long as there's an interface you can talk to from Python, or over standard networking protocols, what's the holdup? Django does not have "out of the box" support for interoperating with every single component someone might want to use, but then neither would an "enterprise" Java framework; that's why you have programmers ;) -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
