We have a use case where there may be a high volume of requests for the same key. Aerospike routes requests to partitions based on a hash of the primary key. Additional partitions and rebalancing can be happen to support higher traffic. However, how can Aerospike handle the case where the hot spotting is caused by a single key?

Is there a better database solution for this case?

CodePudding user response：

This article has some input: https://discuss.aerospike.com/t/hot-key-error-code-14/986.

The first thing is to turn on the [read-page-cache][1], and then spreading between different replicas... or, depending on the use, have multiple copies and reconcile on reads across them (depending if it is a write hotkey or a read one).