Just saw this: http://softwaremaniacs.org/soft/mysql_replicated/en/description/
anybody try it? Looks pre- queryset refactor, don't know if that matters. Vance On Thu, Oct 16, 2008 at 11:17 AM, Vance Dubberly <[EMAIL PROTECTED]> wrote: > Ok just got a huge project that is going to require alot of big iron. > Prolly 4 webservers and at least 2 if not 4 database server and a > memecache server. > > Load balancing across webservers isn't a big deal. But 1 very big > weakness I'm seeing in django as it stands is the ability to deal with > multiple database servers. At the minimum I'm going to have 1 master > and 1 slave mysql server and if the master goes down I'll need to fail > over to the slave. I don't see anyway to manage this in django, am I > missing something? I saw a post on using sqlalchemy to pool > connections perhaps I should be looking there for failover too? > > Vance > > > -- > To pretend, I actually do the thing: I have therefore only pretended to > pretend. > - Jacques Derrida > -- To pretend, I actually do the thing: I have therefore only pretended to pretend. - Jacques Derrida --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
