> or work with. Django provides an incredibly simple framework with a
> multitude of options for different caching and other low level
> implementation decisions (which it achieves through decoupled code)
In addition to Fascis's good comments, if you google for
django shared-nothing
you'll find hits that describe some of the underlying
architecture that should allow multiple instances of Django to be
put behind a load-balancer with minimal fuss. Thus, you should
always be able to scale out by just throwing more
machines/hardware at the problem. Some architectures require
shared state information for session maint. and thus don't scale
to the same degree.
Just a few more thoughts (and one of the reasons I like Django).
-tkc
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
