Question

A gaming leaderboard application stores player statistics in an Amazon DynamoDB table. The read-heavy workload performs the same key-based item lookups repeatedly, and users are complaining about single-digit millisecond latency that the team wants to reduce to microseconds. The reads are eventually consistent and item values change infrequently. Which change requires the least application code effort to meet the latency goal?

Accepted Answer

Add an Amazon DynamoDB Accelerator (DAX) cluster in front of the table and point the DAX SDK client at the cluster endpoint

Answer

Deploy an Amazon ElastiCache for Redis cluster and add application logic to check the cache before every DynamoDB read and update it on writes

Answer

Switch the table to on-demand capacity mode and enable strongly consistent reads

Answer

Create a global secondary index on the frequently read attributes to spread read load