Django数据库可扩展性(Django database scalability)

 我们有一个新的django供电项目，它具有潜在的重交通特性（意味着重型数据库交互）。 所以我们需要提前考虑数据库的可扩展性。 通过一些研究，我们仍然不清楚以下问题： 
 
 
 
 粗粒度：如何为特定的数据库（可能在另一台服务器中）指定一个数据库表（一个django模型）？ 
 
 
 细粒度：如何指定一组表行到特定的数据库（所谓的分片，也可以在另一个数据库服务器中）？ 
 
 
 如何指定写入和读取不同的db？（这将有助于将来的mysql主/从复制） 
 
 
 我们正在寻找解决方案： 
 
 
 
 对应用程序透明（意味着我们不需要在views.py中有其他代码） 
 
 
 应该是ORM级别（意味着只需要在models.py中指定） 
 
 
 兼容当前（或未来）的django版本（为将来升级django保持最小变化） 
 
 
 我还在做研究。 如果我有一些成果，将在以后分享这个帖子。 
 
 希望有经验的人都能回答。 谢谢。 

We have a new django powered project which have a potential heavy-traffic characteristic(means a heavy db interaction). So we need to consider the database scalability in advance. With some researches, the following questions are still not clear to us:
 
 
 
coarse-grained: how to specify one db table(a django model) to a specific db(maybe in another server)?
 
 
fine-grained: how to specify a group of table rows to a specific db(so-called sharding, also can in another db server)?
 
 
how to specify write and read to different db?(which will be helpful for future mysql master/slave replication)
 
 
We are finding the solution with:
 
 
 
be transparent to application program(means we don't need to have additional codes in views.py)
 
 
should be in ORM level(means only needs to specify in models.py)
 
 
compatible with the current(or future) django release(to keep a minimal change for future's upgrading of django)
 
 
I'm still doing the research. And will share in this thread later if I've got some fruits.
 
Hope anyone with the experience can answer. Thanks.

原文：https://stackoverflow.com/questions/1587344