Django database scalability -

We have a new dynamic power project that has a potentially heavy-traffic feature (a heavy DB interaction means). Therefore, we have to understand database scalability in advance. With some research, the following questions are still not clear to us:

1. Broadly: How to make a DB table (a diesen model) for a specific DB (probably in any other server) Please, specify?
2. OK: How to specify a group of table rows for a specific DB (so-called sharding, can also do in other db servers)?
3. How to specify and read

We are finding solutions with this:

1. To be transparent to the application program ( This means that we do not have to have additional code in the idea)
2. must be in the ORM level (this only means to specify in models.py)
3. Current Compatible with (or future) of the demo release (Keeping the minimum change of the regime for future upgrades For the sector)

I will share still am researching and later in the formula that will give me some fruit.

Hope that anyone can answer with experience. Thank you.

Do not forget about caching. Using a memkach to relieve your DB load is the key to creating a high performance site.

As Alex said, the Digengo-Core does not support your specific requests for those features, although they are definitely on the list.

If you do not do this application layer, you are basically asking for performance problems. There are not any good open source automation layers for this type of work, because it breaks SQL SQLs. If you are really worried about it, then you should coding the whole app for it, not just expecting that your ORM will take care of it.