A city stores every parking ticket under the DynamoDB partition key CITY#ALL, causing a hot partition during ticket season. How should the key design change?
Select an answer to reveal the explanation.
Short Explanation
CITY#ALL is one overstuffed filing cabinet—everyone slams the same drawer in ticket season. Spread keys across many ticket IDs (high cardinality) so DynamoDB can use many partitions. A key named HOT just brags about the problem.
Full Explanation
DynamoDB partitions scale with distinct partition-key values. Low-cardinality keys such as a single CITY#ALL value create hot partitions under load. High-cardinality keys distribute throughput. Concentrating writes further or abandoning DynamoDB for a single local file does not fix partition balance.