Great. Thanks.
On Apr 19, 7:59 am, Alex Koshelev <[email protected]> wrote:
> There is an existing production-ready application [1] that allows you
> to use MySQL replication facilities. It is formed as django database
> backend with some additional functional.
>
> We use it for our high-load Django powered content services.
>
> [1]:http://softwaremaniacs.org/soft/mysql_replicated/en/
>
> On Sun, Apr 19, 2009 at 3:55 PM, Continuation <[email protected]> wrote:
>
> > In the Django Book, it is stated that:
> >http://www.djangobook.com/en/2.0/chapter12/
>
> > "As you need more database performance, you might want to add
> > replicated database servers. MySQL includes built-in replication"
>
> > But how exactly would MySQL replication work with Django?
>
> > According to MySQL doc:
> >http://dev.mysql.com/doc/refman/5.1/en/replication-solutions-scaleout...
>
> > "Change the implementation of your database access to send all writes
> > to the master, and to send reads to either the master or a slave."
>
> > So it is the application's responsibility to direct DB writes to
> > master & reads to either master or slave. But since Django doesn't
> > support multiple database access, this wouldn't work.
>
> > So what does the Django book mean by "you might want to add replicated
> > database servers" if Django doesn't support accessing replicated
> > databases?
>
> > Does anyone have django setup that uses replicated DB? would love to
> > hear your experiences.
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to [email protected]
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
-~----------~----~----~----~------~----~------~--~---
