1 / 4 Hot Partitions & The Celebrity Problem

Sprinkle the Key

A like counter for one viral post is a single row taking 40,000 updates per second and saturating its partition. Your team starts appending a random suffix from 0 to 63 to that partition key. What did the change buy, and what did it cost?

A

Total write volume drops because updates to the same suffix are coalesced, so no read path change is needed at all

B

Writes now spread over as many as 64 partitions, but reading the total requires fetching all 64 suffixed rows and summing them

C

Writes now spread over 64 partitions and reads stay a single lookup, because the suffix is derived from the identity of the reader

D

Reads stay a single cheap lookup, but every write now needs a distributed transaction across all 64 suffixes to stay consistent