A city portal repeatedly reads the same reference data from Amazon RDS, driving a costly sprawl of read replicas. What cost-aware alternative should the architect evaluate?
Select an answer to reveal the explanation.
Short Explanation
If every page asks RDS the same question, stop hiring more replica waiters—put ElastiCache at the door. Caching hot reads is often cheaper than replica sprawl.
Full Explanation
ElastiCache (Redis or Memcached) offloads repeated read-heavy patterns from RDS, often reducing the need for many read replicas and their instance cost. Unlimited replica growth is expensive; disabling Multi-AZ harms availability rather than optimizing reads; cookies are not a secure or complete reference-data store.