Hot fee-schedule reads hammer Aurora during business hours for a city cashiering app. What application-level change reduces database load?
Select an answer to reveal the explanation.
Short Explanation
Fee schedules barely change by the minute, but cashiers hit them constantly—classic cache win. Park the hot reads in ElastiCache and let Aurora breathe. Same answers, far less database thrash.
Full Explanation
Application-level caching with Amazon ElastiCache absorbs repeated reads of relatively stable data such as fee schedules, reducing Aurora load and latency during business hours. Scanning on every keystroke, shutting the database down, or cloning cross-Region per request increases cost and risk. Caching is a core Domain 4 optimization technique for read-heavy paths.