13 ms·
i think the standard recommendation is to do range partitioning on the hash of the key, aka hash range partitioning (i know yugabyte supports this out of the bo
by findjashua 1y ago
i think the standard recommendation is to do range partitioning on the hash of the key, aka hash range partitioning (i know yugabyte supports this out of the box, i'd be surprised if others don't). this prevents the situation of all recent uuids ending up on the same shard.
- kbolino 1y agoIndeed. In fact, Cassandra and DynamoDB have both hash keys and range keys; I've edited my comment to be more specific.