Caching and messaging

Redis vs Memcached

Redis has 9 supported release lines and Memcached has 1. Redis 8.0 reaches end of life on Dec 1, 2026. Redis offers RSALv2, SSPL-1.0 or AGPL-3.0; Memcached is open source (BSD-3-Clause).

Last checked against endoflife.date and deps.dev.

Side by side

Every value links to its source. Where a row doesn’t apply to one of them, the cell says why.

Support and releases
RedisMemcached
Supported release lines

9 lines: 8.10, 8.8, 8.6, 8.4, 8.2 and 4 more

Next to end: 8.0 on Dec 1, 2026

endoflife.date

Only the newest, 1.6

No end dates published

endoflife.date

Latest release

8.10.2

Released Sep 17, 2026

endoflife.date

1.6.45

Released Jul 9, 2026

endoflife.date

Releases in the last 12 months

4 new release lines

Patch releases aren’t counted

endoflife.date

No new release lines

Patch releases aren’t counted

endoflife.date

Security
RedisMemcached
Advisories published in the last 12 months

Not tracked as a package on OSV.dev

Security advisories

Not tracked as a package on OSV.dev

OpenSSF Scorecard

6.9 / 10

redis/redis, Aug 24, 2026

Scorecard

4.5 / 10

memcached/memcached, Aug 24, 2026

Scorecard

Licence and hosting
RedisMemcached
Licence

RSALv2, SSPL-1.0 or AGPL-3.0

Open source under the AGPL-3.0 option

AGPLv3 is OSI-approved, but you must publish your changes if you serve a modified Redis over a network. Versions 7.4–7.x are RSALv2 / SSPLv1 only.

redis.io

BSD-3-Clause

Open source (permissive)

deps.dev

How you run it

Self-hosted, or Redis Cloud, the vendor’s managed service

Self-hosted, or managed by Amazon ElastiCache and Google Cloud Memorystore

Adoption
RedisMemcached
GitHub stars

76.8K

redis/redis

GitHub

14.3K

memcached/memcached

GitHub

Which fits your constraints

Read across for what matters to you. Each answer comes from the data above or the project’s licence and hosting options.

How Redis and Memcached fit common constraints
RedisMemcached
An open-source licence

Yes: Under the AGPL-3.0 option

Yes: BSD-3-Clause

Someone else runs it for you

Yes: From Redis Cloud

Yes: From Amazon ElastiCache and Google Cloud Memorystore

You can run it on your own servers

Yes: Yes, it’s software you install

Yes: Yes, it’s software you install

A long support window

8.2 is supported until Sep 1, 2030

Only the newest line (1.6); no end dates published

What each is good at

Redis

In-memory data store with pub/sub, persistence, and Lua scripting

Strengths

  • Rich data structures (lists, sets, sorted sets, hashes)
  • Built-in pub/sub messaging
  • Optional persistence to disk
  • Lua scripting support
  • Widely adopted with extensive tooling

Trade-offs

  • Single-threaded (can bottleneck on CPU)
  • Memory-intensive for large datasets
  • Persistence adds latency overhead

Common uses

  • Session storage
  • Real-time analytics
  • Leaderboards
  • Pub/sub messaging

Memcached

Simple, high-performance distributed memory caching system

Strengths

  • Extremely fast for simple key-value operations
  • Multi-threaded architecture scales well
  • Low memory overhead
  • Easy to set up and manage

Trade-offs

  • Only supports simple key-value storage
  • No persistence - data lost on restart
  • No built-in replication or clustering
  • Limited data structure support

Common uses

  • Page caching
  • Database query caching
  • Session storage (ephemeral)

From StackPrism’s curated notes. Pricing isn’t covered here: it changes often, so check each vendor’s pricing page.

When teams weigh these two

Both are in-memory caches you put in front of a database. Memcached is a deliberately simple key-value cache; Redis adds data structures (lists, sets, sorted sets, streams), optional persistence and pub/sub, so it often doubles as a queue or session store.

How this comparison works

Release lines and end-of-life dates come from endoflife.date, release counts from deps.dev’s publish dates, and advisories from OSV.dev, counted once per flaw even when it’s listed under several ids, and checked against CISA’s list of vulnerabilities known to be exploited. Status and incident history come from each vendor’s public status feed; licences from each project’s licence file or the vendor’s licensing page, linked in the table.

The data refreshes every few hours and the time it was checked is shown above. There’s no pricing and no overall winner: which one fits depends on your constraints. To see how the versions you actually run hold up, check your repo.

Already using one of them?

Paste a public GitHub repo and see what’s vulnerable, end of life or deprecated in it today. Free, no sign-up.