A legacy inspector-scheduling database in the public-works account…

Question

A legacy inspector-scheduling database in the public-works account is overwhelmed by repeated reads of hot keys such as open time slots and session data after more field tablets came online. Which modernization enhancement should architects add without a full schema rewrite?

Accepted Answer

Place Amazon ElastiCache in front of the chatty legacy database for hot keys and session cache — If the same open-slot row gets asked a thousand times, that's a sticky note on the counter, not another trip to the filing room. ElastiCache holds those hot keys so the old database can breathe. A bigger box still answers the same chatty questions.

Answer

Double the RDS instance class only and leave every hot key hitting the database

Answer

Disable all application caching so the database remains the only source of truth for every page

Answer

Export the live schedule to Amazon S3 Glacier Deep Archive and query it for each tablet refresh

A legacy inspector-scheduling database in the public-works account is overwhelmed by repeated reads of hot keys such as open time slots and session data after more field tablets came online. Which modernization enhancement should architects add without a full schema rewrite?

Short Explanation

Full Explanation