A product page frequently executes the same expensive relational lookup. A few seconds of stale product-description data is acceptable. The database remains the system of record. Which design best reduces repeated database work?

1. Add a Multi-AZ standby and send reads to it without changing the application endpoint.
2. Run the lookup more often so database pages never become cold.
3. Use an ElastiCache-backed cache-aside pattern with a suitable TTL and invalidation on relevant updates.
4. Use sticky ALB sessions while leaving all product lookups uncached in the same relational database.