Thank Kemuri, MySQL cluster seems very cool, but I'm not sure it is the best solution if the DB is split over different networks . Latency might be an issue with the synchronous setup that MySQL cluster provides.
Having looked at it a bit further since my post I am considering "circular replication" with a master on each network and slaves under each master (based on what Julio mentioned). Using this type of setup I am hoping to test out Amazon's EC2 as a way to scale Django apps. There's an interest article on setting up circular replication at http://www.onlamp.com/pub/a/onlamp/2006/04/20/advanced-mysql-replication.html MerMer kemuri wrote: > hey Merric, > > On Apr 9, 4:10 am, Merric Mercer <[EMAIL PROTECTED]> wrote: > >> The django book's chapter on deployment mentions the use of Database >> replication as a means to scale using MySQL. >> >> > > If you want to try something cool, try MySQL Cluster, and better 5.1 > since it has disk-based support instead of only in-memory. You will > need to do some modifications to the CREATE TABLE if you want to go > that way, but well.. > > Basically if comes to this that you have 2 data nodes which store data > and in the MySQL servers you have tables using the NDB engine. This > means that you can add like 40 MySQL servers all using the same data, > at the same time. > > Anyway, this is a bit advanced MySQL.. And it's not really a Django > matter indeed. > > Best regards, > > Geert > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
