You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 29, 2025. It is now read-only.
From skimming the source code I think this package directs writes to a master database and then shuffles a list of slave dbs to direct all reads to. My main confusion is in the word, 'replicated' in the package title. I am guessing the programmer/architect of the target Django App must use some other setup to actually replicate data from a master to a set of slaves. And you would do this to distribute load on a very busy Django app?
None of this is described on the README page but seems like the essence of django_replicated.
From skimming the source code I think this package directs writes to a master database and then shuffles a list of slave dbs to direct all reads to. My main confusion is in the word, 'replicated' in the package title. I am guessing the programmer/architect of the target Django App must use some other setup to actually replicate data from a master to a set of slaves. And you would do this to distribute load on a very busy Django app?
None of this is described on the README page but seems like the essence of django_replicated.