Re: Sharding DB: one database per user dynamically

> Den 6. okt. 2016 kl. 15.34 skrev Stefano Tranquillini <stefano.tranquillini@gmail.com>:
>
> Well, not really.
>
> I would like to shard the db, but probably i can just build a function to write on DB1 or DB2 depending on the user id, this should be feasible, isn't it?

Yes, that would be feasible, of course. You could use standard Django routing if it fits your requirements, or implement your own.

You just haven't come up with a convincing argument for why you need the sharding. Sharding is normally something you use when dealing with enormous amounts of data, for performance reasons, not business logic. It goes beyond just splitting data into multiple databases with identical schemas, BTW. https://en.wikipedia.org/wiki/Shard_(database_architecture)

Erik

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/68D4DAFA-9627-4682-BC8E-E2FFC179892A%40cederstrand.dk.
For more options, visit https://groups.google.com/d/optout.