A gaming company runs a leaderboard service backed by an Amazon DynamoDB table. During tournaments, the same set of player records is read millions of times per minute, causing high read capacity consumption and occasional throttling. Read latency has climbed into the low milliseconds, but the application requires microsecond-level response times for repeated reads. Writes remain relatively infrequent. Which solution best meets these requirements with the least application change?