replication isnt exactly distributing... with only one master db which handles all the writes you have a single point of failure...
On 7 Juni, 20:05, Jeff Anderson <[EMAIL PROTECTED]> wrote: > lgr888999 wrote: > > Great write up! Thanks! Im fully aware of that the problem is in the > > datastorage but django doesnt support for example sharding or multiple > > databases out of the box, the other way around its more about keeping > > things dry and normalized which makes it harder to build something > > decentralized. Hence this post to see if someone succeded with such a > > setup. > > Many databases support replication, and you can use an SQL proxy that is > smart enough for load balancing. > > Chapter 20 in the Django Book details this. The authors have implemented > a distributed django system.http://www.djangobook.com/en/1.0/chapter20/ > About halfway down there is a section header "scaling". > > Hope this helps! > > Jeff Anderson > > signature.asc > 1KHämta --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
