5 ms·
more recent customers/users/accounts probably do more actions than very old accounts though, how is that not also eventually creating uneven shards?
by Nathanba 4y ago
more recent customers/users/accounts probably do more actions than very old accounts though, how is that not also eventually creating uneven shards?
- preseinger 4y agoyou're right, uneven shards are an inevitable outcome of this approach but shard "even-ness" is in direct tension with the concern of the GP, which is execution atomicity frequently, it's better to have uneven shards (that you can e.g. scale independently when necessary) that give you atomic execution, than even shards that require distributed transactions
- AdieuToLogic 4y agoWhile high volume multi-tenant "customers/users/accounts" systems are common, they are not the only ones which benefit from sharded persistent stores. For example, consider a system which monitors farm equipment for Caterpillar and John Deere. Lets say each company has 100k devices which send one message per day to the system. While it is easy to envision sharding device messages based on "DeviceId / Company" in this hypothetical system, there would be no value sharding the two customers.