For access to my API user should send login and password and get generated token for access.
Account login password
Suppose the size of account's table is very large. So large - so needs sharding.
Usually I prefer sharding by ranges (which excludes re-sharding) when I do it for tables with primary key
ID (and the same shard key). But in this case sharding key should be a string (
What is the last best practices you use for this task?
Consistent hashing (from Guava, for example) and resharding only
(K / n) keys in the case of changing structure of nodes? May be there are some practices without re-sharding? Something else?