Good
Rating: 8 out of 10
IncentivizedUse Cases and Deployment Scope
In our services, some of the information inside the database is not required to retrieve frequently from there. In such cases, we use ElastiCache in order to reduce the load from the database especially RDS.
Pros
- configuration data
- user login detail data
- application permission data
Cons
- not to get lost cache data in order to change ElasitCache instance type
- most of the time cache data are not distributively stored to secondary, mostly goes to primary
- default TTL should be 30 days or 60 days instead of infinity
Likelihood to Recommend
Not to get lost data when ElastiCache instance type changed and reduce the timeframe as 3 mins or 5 mins when instance type changed as well.