Good
Updated September 14, 2023
Good
Score 8 out of 10
Vetted Review
Verified User
Overall Satisfaction with Amazon ElastiCache
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.
- configuration data
- user login detail data
- application permission data
- 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
- obviously fast to retrieve data
- able to reduce waiting time instead of RDS
- able to reduce cost by the way of using some data in RDS
- memcached should be improved like Redis
- need serverless with Aurora RDS
- cost should be decreased
In order to save some login information, notification alert, and some other critical data, we used DynamoDB instead of ElastiCache due to low cost and data are more persistent as compared with ElastiCache.
Do you think Amazon ElastiCache delivers good value for the price?
Not sure
Are you happy with Amazon ElastiCache's feature set?
Yes
Did Amazon ElastiCache live up to sales and marketing promises?
Yes
Did implementation of Amazon ElastiCache go as expected?
Yes
Would you buy Amazon ElastiCache again?
Yes