AWS ElastiCache - Redis vs Memcached
Redis
-manual and automatic snapshots
-provides presistence storage and is a replament for DB)
Memcached
-purely a caching solution and uses DB as the origin of the data)
Steps required to migrate the app to use ElastiCached with minimal changes
-update the config file with endpoint to use Amazon ElastiCached cluster
-configure a SG to allow access from the app servers
Redis -> provides natve functions that simply the deveroment of leader bords
Memcached -> it is to more defficule to sort and rank large dataset
Redshift and S3
- are not designed for high volumes of small reades and writes, typical to mobile ....
Expanding web fleet and cache fleet multiple times over the next year to accomodate increased user traffic. How do you minimaze the amount of changes required when scaling event occures?
Configure AutoDiscovery on the client side.
When the clients are configured to use AutoDiscovery, they discover new cache nodes as they are added or removed. AutoDiscovery must be configured on each client and is not active server side, Updating the configuration file each time will be very difficult to manage.
https://d1.awsstatic.com/whitepapers/performance-at-scale-with-amazon-elasticache.pdf


Komentarze
Prześlij komentarz