Amazon ElastiCache

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search
Amazon ElastiCache (EFS)
Developer(s)Amazon.com
Initial releaseAugust 22, 2011; 8 years ago (2011-08-22).[1]
Available inEnglish
TypeCloud Storage
Websiteaws.amazon.com/elasticache/


Amazon ElastiCache is a fully managed in-memory data store and cache service by Amazon Web Services (AWS). The service improves the performance of web applications by retrieving information from managed in-memory caches, instead of relying entirely on slower disk-based databases. ElastiCache supports two open-source in-memory caching engines: Memcached and Redis (also called “ElastiCache for Redis”).[2]

As a web service running in the computing cloud, Amazon ElastiCache is designed to simplify the setup, operation, and scaling of memcached and Redis deployments. Complex administration processes like patching software, backing up and restoring data sets and dynamically adding or removing capabilities are managed automatically. Scaling ElastiCache resources can be performed by a single API call.[3]

Amazon ElastiCache was first released on 22 August 2011,[4] supporting memcached. This was followed by support for reserved instances on 5 Apr 2012[5] and Redis on 4 Sep 2013.[6]

Uses[edit]

As a managed database service with multiple supported engines, Amazon ElastiCache has a wide range of uses, including

Performance acceleration[edit]

Database limitations are often a bottleneck for application performance. By placing Amazon ElastiCache between an application and its database tier, database operations can be accelerated.[7]

Cost reduction[edit]

Using ElastiCache for database performance acceleration can significantly reduce the infrastructure needed to support the database. In many cases, the cost savings outweigh the cache costs. Expedia was able to use ElastiCache to reduce provisioned DynamoDB capacity by 90%, reducing total database cost by 6x.[8][9]

Processing time series data[edit]

Using the Redis engine, ElastiCache can rapidly process time-series data, quickly selecting newest or oldest records or events within range of a point-in-time.[10]

Leaderboards[edit]

Leaderboards are an effective way to show a user quickly where they currently stand within a gamified system. For systems with large numbers of gamers, calculating and publishing player ranks can be challenging. Using Amazon ElastiCache with the Redis engine can enable high-speed at scale for leaderboards.[11]

Rate limitation[edit]

Some APIs only allow a limited number of requests per time period. Amazon ElastiCache for Redis engine can use incremental counters and other tools to throttle API access to meet restrictions.[12]

Atomic counter[edit]

Programs can use incremental counters to limit allowed quantities, such as the maximum number of students enrolled in a course or ensuring a game has at least 2 but not more than 8 players. Using counters can create a race condition where an operation is allowed because a counter was not updated promptly. Using the ElastiCache for Redis atomic counter functions, where a single operation both checks and increments the counter’s value, prevents race conditions.[13]

Chat rooms and message boards[edit]

ElastiCache for Redis supports publish-subscribe patterns, which enable the creation of chat rooms and message boards where messages are automatically distributed to interested users.[14]

Deployment Options[edit]

Amazon ElastiCache can use on-demand cache nodes or reserved cache nodes.

On-demand nodes provide cache capacity by the hour, with resources in the AWS cloud assigned when a cache node is provisioned. An on-demand node can be removed from service by its owner at any time. Each month, the owner will be billed for the hours used.[15]

Reserved nodes require a 1-year or 3-year commitment, which dedicates cache resources to the owner. The hourly cost of reserved nodes is significantly lower than the hourly cost of on-demand nodes.[16]

Performance[edit]

An efficient cache can significantly increase application’s performance and user navigation speed. Amazon CloudWatch exposes ElastiCache performance metrics that can be tracked.[17]

Key performance metrics[edit]

  • Client metrics (measure the volume of client connections and requests): Number of current client connections to the cache, Get and Set commands received by the cache
  • Cache performance: Hits, misses, Replication Lag, Latency
  • Memory metrics: Memory usage, Evictions, Amount of free memory available on the host, Swap Usage, Memory fragmentation ratio
  • Other host-level metrics: CPU utilization, Number of bytes read from the network by the host, Number of bytes written to the network by the host

Metric collection[edit]

Many ElastiCache metrics can be collected from AWS via CloudWatch or directly from the cache engine, whether Redis or Memcached, with a monitoring tool integrating with it:[18]

Using the online management console is the simplest way to monitor ElastiCache with CloudWatch. It allows to set up basic automated alerts and to get a visual picture of recent changes in individual metrics.

Metrics related to ElastiCache can also be retrieved using command lines. It can be used for spot checks and ad hoc investigations.

  • Monitoring tool integrated with CloudWatch

The third way to collect ElastiCache metrics is via a dedicated monitoring tool integrating with Amazon CloudWatch.

Notable Customers[edit]

Users of Amazon ElastiCache include Airbnb[19], Expedia[20], Zynga[21], FanDuel[22] and Mapbox[23]

Limitations[edit]

As an AWS service, ElastiCache is designed to be accessed exclusively from within AWS, though it is possible to connect the service to applications and databases that are not hosted by AWS.[24]

Alternatives[edit]

Other vendors provide cloud data cache services comparable to Amazon ElastiCache, including Azure Cache for Redis, Redis Labs (company behind open source Redis and Redis Enterprise), Redis To Go, IBM Compose, Oracle Application Container Cloud Service, openredis, Redis4You, RedisGreen and Rackspace ObjectRocket.

References[edit]

  1. ^ "Amazon ElastiCache – Distributed In-Memory Caching". Amazon Web Services. 22 August 2011.
  2. ^ "ElastiCache for Redis". Amazon Web Services. Retrieved 2016-08-29.
  3. ^ "Scaling". AWS ElastiCache Documentation. Retrieved 2016-07-08.
  4. ^ "Amazon ElastiCache – Distributed In-Memory Caching". amazon.com. Retrieved 2016-07-08.
  5. ^ "Reserved Cache Nodes for Amazon ElastiCache". amazon.com. Retrieved 2016-07-08.
  6. ^ "Amazon ElastiCache – Now With a Dash of Redis". amazon.com. Retrieved 2016-07-08.
  7. ^ "Use Memcached to improve database performance". CloudVPS. Archived from the original on 2016-07-13. Retrieved 2016-07-08.
  8. ^ "Customer Testimonials". amazon.com. Retrieved 2016-07-08.
  9. ^ "AWS Building Scalable Applications on AWS NoSQL Services". youtube.com. Retrieved 2016-07-08.
  10. ^ "Using Redis as a Time Series Database: Why and How". InfoQueue. Retrieved 2016-07-08.
  11. ^ "USING REDIS TO BUILD YOUR GAME LEADERBOARD". Social Point. Retrieved 2016-07-08.
  12. ^ "DOWN BOY: HOW TO EASILY THROTTLE REQUESTS TO AN API USING REDIS". Collective Idea. Retrieved 2016-07-08.
  13. ^ "An Atomic Rant". Nate Wigel vs Technology. Retrieved 2016-07-08.
  14. ^ "Create a Simple Chat Room with Redis Pubsub". Program Every Day. Retrieved 2016-07-08.
  15. ^ "Amazon ElastiCache Pricing". amazon.com. Retrieved 2016-07-08.
  16. ^ "ElastiCache Reserved Cache Nodes". amazon.com. Retrieved 2016-07-08.
  17. ^ "Monitoring ElastiCache performance metrics with Redis or Memcached". Retrieved 2016-10-24.
  18. ^ "Collecting ElastiCache metrics + its Redis/Memcached metrics". Retrieved 2016-10-24.
  19. ^ "Airbnb Case Study". amazon.com. Retrieved 2016-07-08.
  20. ^ "Building Scalable Applications on AWS NoSQL Services". youtube.com. Retrieved 2016-07-08.
  21. ^ "AWS Case Study: Zynga". amazon.com. Retrieved 2016-07-08.
  22. ^ "FanDuel Case Study". amazon.com. Retrieved 2016-07-08.
  23. ^ "Building Scalable Applications on AWS NoSQL Services". youtube.com. Retrieved 2016-07-08.
  24. ^ "Accessing ElastiCache Resources from Outside AWS". AWS Documentation. Retrieved 2016-07-08.

External links[edit]