A read-heavy open-data catalog hammers Aurora with identical queries for popular datasets. What application-level change reduces database load?
Select an answer to reveal the explanation.
Short Explanation
If everyone asks for the same popular dataset, stop poking the database every time—park the answer in ElastiCache and serve the crowd from memory.
Full Explanation
ElastiCache provides an in-memory cache for frequently read results, cutting repetitive Aurora load. Scaling storage alone does not remove identical query load; Scans are inefficient substitutes for relational catalog queries; forcing all traffic to the writer worsens contention.