Neutralizing hotspots
Neutralizing a hotspot: three fixes
Isolate the hot key
Random prefix
Adaptive management
WHAT IT DOES
hot key gets its own
shard (own machine)
range schemes only
key to 100 suffixed keys
writes fan out
00..99 suffix
cloud moves load
automatic balancing
DynamoDB-style
PRICE
must detect hot keys
heat moves over time
one machine per key
reads merge 100 keys
writes only, not reads
needs hot-key tracking
opaque behavior
vendor-specific
surprises possible
FITS
rare, known hot keys
write-hot counters
managed clouds
hashing spreads keys, not load · write-hot differs from read-hot