A product catalog is read very frequently and the same results are requested repeatedly.
Reduce database read load and latency.
Which design is most appropriate?
Placing Amazon ElastiCache between the application and database can return frequently used results from memory and reduce repeated database reads.
Detailed explanation
Archive storage does not provide a low-latency application cache.
Archive storage does not provide a low-latency application cache.
ElastiCache stores frequently accessed data in memory for low-latency reads.
ElastiCache stores frequently accessed data in memory for low-latency reads.
DNS records are not an in-memory application cache.
DNS records are not an in-memory application cache.
Continuing to send reusable results to the database does not reduce its load.
Continuing to send reusable results to the database does not reduce its load.
Check official documentation
Compare the following points with the official documentation.
Amazon ElastiCacheのキャッシュ用途とデータアクセスパターンの公式説明を確認する。
What to confirm
読み取り負荷の高いデータにインメモリキャッシュを組み込める。
Key points
- Amazon ElastiCache
- In-memory cache
- Read load
Notes
- Environment: AWS公式ElastiCacheドキュメントの確認
- Confirm current AWS service behavior and architecture guidance in the official documentation.
Foundation review
Origin offload
Cache hits reduce database queries and can lower response latency.
Cache responsibility
The cache accelerates access but does not automatically replace the database as the system of record.