Django Redundancy
Posted
by
Sunsu
on Stack Overflow
See other posts from Stack Overflow
or by Sunsu
Published on 2011-01-10T04:47:24Z
Indexed on
2011/01/10
4:53 UTC
Read the original article
Hit count: 210
I've read many things about scaling Django and the new multiple-DB support makes it so much easier. However, I have not been able to find much information on good ways to create a fully redundant system (not just one that scales).
I realize there are many things that go into this problem, but the real thing I'm having trouble solving well is Database redundancy.
Is it possible to set up a "write slave" using django's new multiple-DB support? If I had IP failover support it seems like having a write slave would help solve the problem. Simple MySQL replication doesn't seem like it will work due to slave lag right?
What's the typical method of creating a redundant database system? Any input or guidance you guys have would be greatly appreciated. I realize I could be asking the wrong questions!
© Stack Overflow or respective owner