A county property-search site is read-heavy against Amazon RDS and frequently repeats the same queries. How should the architect improve database read performance?
Select an answer to reveal the explanation.
Short Explanation
Repeating the same property lookups shouldn’t hammer the database every time—cache them. ElastiCache in front of RDS soaks up those hot reads and protects the DB. Killing indexes, parking the DB on instance store, or making every read a write path goes the wrong way.
Full Explanation
Amazon ElastiCache provides an in-memory cache that absorbs repeated read traffic and reduces load on relational databases. For read-heavy property search, caching frequent results improves latency and shields RDS. Removing indexes, using ephemeral instance store as the system database, or conflating write paths with read acceleration are incorrect performance designs.