Tim,
Thanks for the helpful answers.
As for specific details about my app, right now I'm still in the
design phase. It will start small, but hopefully it will get popular
quickly. So I don't know how big the Db will be or how many users will
there be.
What I'm trying to do is to make sure
> Recently I found out Django doesn't support multiple databases. That's
> quite surprising.
>
> Given that limitation, how do you scale out a Django app?
Depends on where your bottleneck(s) is/are. It also depends
heavily on your read/write usage pattern. If you're truly
experiencing a
Recently I found out Django doesn't support multiple databases. That's
quite surprising.
Given that limitation, how do you scale out a Django app?
Without multi-DB support, most of the usual techniques for scaling out
such as:
- DB sharding
- functional partitioning - eg. separate DB
3 matches
Mail list logo