A permit-search API misses its p99 latency SLO. CloudWatch and Dyna…

Question

A permit-search API misses its p99 latency SLO. CloudWatch and DynamoDB metrics show a few partition keys absorbing most traffic. Which performance improvement best addresses the bottleneck?

Accepted Answer

Identify hot keys/partitions, redesign access patterns or key design as needed, and add an appropriate cache (for example DynamoDB Accelerator or application caching) for hot reads. — Hot keys are the one checkout lane with twenty carts while other lanes sit empty. Fix the key design or fan-out pattern, then put a cache in front of the celebrities. p99 calms down when the crowd stops crushing one partition.

Answer

Switch the table to eventual consistency only and ignore p99 latency as a vanity metric.

Answer

Delete CloudWatch latency metrics so the SLO appears healthy on dashboards.

Answer

Force all traffic through a single Lambda in one Availability Zone to simplify tracing.

A permit-search API misses its p99 latency SLO. CloudWatch and DynamoDB metrics show a few partition keys absorbing most traffic. Which performance improvement best addresses the bottleneck?

Short Explanation

Full Explanation