Citizens see intermittent ProvisionedThroughputExceeded during enrollment peaks. Besides blind retries, what should developers address?
Select an answer to reveal the explanation.
Short Explanation
Retries help a blip; they don’t fix a hot partition or an undersized table. Check keys, capacity mode, and caching so enrollment peaks stop lighting the throttle lamp.
Full Explanation
ProvisionedThroughputExceeded indicates capacity or partition imbalance. Remediation includes hotter-key analysis, on-demand or higher provisioned/autoscaled capacity, and read caching—retries alone are insufficient. Deleting tables, inventing “eventually consistent writes,” or hiding metrics do not solve throttling.