What is Amazon ElastiCache? A plain-English explainer

What an in-memory cache actually does

A cache stores a copy of data in memory (RAM) rather than on disk, so reading it back is very fast. The trade-off is that memory is temporary and comparatively limited: a cache is not meant to be the permanent, authoritative copy of your data, and it can be resized, evicted or lost without that being a disaster, because the real data still lives safely in a database behind it. Our what-is-caching explainer covers this general idea in more depth; ElastiCache is AWS’s managed way of running that pattern at production scale.

The practical effect is that an application checks the cache first for something it needs. If the data is there (a “cache hit”), it comes back almost immediately. If it is not (a “cache miss”), the application fetches it from the database, and often writes a copy into the cache so the next request is fast. Done well, this means only a fraction of requests ever have to wait on the slower database.

ElastiCache is a cache, not a database

This is the distinction worth holding onto: ElastiCache accelerates a database, it does not replace one. The database remains the durable, authoritative source of truth — the place data is safely stored long-term, with backups and consistency guarantees. ElastiCache holds a fast, temporary, in-memory copy of some of that data, positioned in front of the database to absorb the read traffic that would otherwise hit it directly.

That said, Redis in particular is flexible enough that some teams use it for more than pure caching — as a fast, temporary data store for specific patterns such as counters or short-lived session data. Even then, the underlying idea holds: it is fast, in-memory and not meant to be the sole, permanent copy of anything you cannot afford to lose.

Common uses

ElastiCache shows up in a handful of recurring patterns. Session stores keep a logged-in user’s session data in memory so every page load does not need a database round trip. Leaderboards and counters use Redis’s fast, atomic data structures to update and read rankings or tallies with minimal delay. Caching query results — storing the output of an expensive or frequently repeated database query — is the most general use, and the one most applications reach for first as traffic grows.

• Session stores — keeping logged-in user session data fast to read
• Leaderboards and counters — using Redis’s in-memory data structures
• Caching database query results to reduce repeated load
• Reducing latency for data that is read far more often than it changes

Redis/Valkey versus Memcached

ElastiCache offers two engines, and the choice between them is really a choice of how much you need from the cache. Memcached is simple and purely a cache: fast, straightforward, good for the plainest caching needs. Redis (and its open-source fork Valkey, which ElastiCache also supports) is considerably richer — it adds data structures beyond simple key-value pairs, persistence options, and features that support patterns like leaderboards and pub/sub messaging. Most new ElastiCache workloads choose Redis or Valkey for that flexibility unless the need really is the simplest possible cache.

How you pay for it, without the numbers

ElastiCache follows AWS’s usual pay-for-use model: you provision nodes of a chosen size and are billed for the capacity and time they run, similar in spirit to how EC2 is billed. Exact node sizes and rates change over time, so this article deliberately does not list them — check AWS’s ElastiCache pricing page for current detail. The concept to take away is that a cache sized to match real traffic, and switched off or downsized when it is not needed, is what keeps this cost-effective.

Where ElastiCache appears in certification study

ElastiCache appears on the AWS Certified Solutions Architect – Associate exam as part of designing performant, cost-efficient architectures — recognising when adding a cache in front of a database is the right fix for a latency or load problem is a recurring scenario. AWS Certified Developer – Associate covers the application-level side: how an application checks and populates a cache, and the trade-offs of caching strategies.

This article covers what ElastiCache is and why it exists — the deeper detail of engine choice, replication and eviction policies belongs in the syllabus itself. Our /revision study library breaks that down lesson by lesson for the certifications below.