Redis vs Memcached vs Valkey: A 2026 Decision Guide
Memcached if it's truly just a cache. Redis if you need anything more. Valkey if SSPL or AGPLv3 blocks you. Here's the matrix.
At a glance: which wins per need
| If you need... | Pick |
|---|---|
| Pure ephemeral cache, simple GET/SET, max throughput | Memcached |
| Session store, rate limiter, leaderboard, queue | Redis |
| Pub/sub, real-time messaging | Redis or Valkey |
| Vector search, AI / RAG workloads | Redis 8.0 |
| OSI-compliant open source mandate | Valkey |
| Already on AWS ElastiCache or Google Memorystore | Valkey |
Quick decision tool
Sessions need persistence + replication. Memcached restart wipes all sessions. Redis (or Valkey) is the only safe choice.
The 2026 state of play
Redis 8.0 (May 2025)
Redis is now tri-licensed: RSALv2, SSPLv1, and AGPLv3. The AGPLv3 addition (May 2025) makes Redis OSI-compliant again for the first time since March 2024 but AGPLv3's network copyleft is uncomfortable for many commercial shops. Redis 8.0 adds vector sets (HNSW-based similarity search for AI/RAG), hash field TTL, and vendor-claimed latency improvements up to 78% on bitmaps. Benchmark vendor-sourced numbers with your own workload before committing.
Memcached 1.6.x (BSD, never moved)
Memcached has been BSD-licensed since 2003 and never changed. Actively maintained in 2026. Facebook runs the world's largest Memcached deployment. Its lane is narrow but real: multi-threaded raw GET/SET throughput, simple ephemeral page caching, lower per-item memory overhead. If your only need is a fast, simple, ephemeral cache and you need BSD permissiveness, Memcached still earns its place.
Valkey 8.1 (BSD, early 2026)
The Linux Foundation fork of Redis 7.2.4, backed by AWS, Google Cloud, Oracle, and Ericsson. Launched April 2024 when Redis dropped BSD. Valkey 8.0 redesigned threading for ~30-35% throughput improvement and 230% RPS gain over 7.2 on Graviton3. Valkey 8.1 shows ~28% lower memory at 50M sorted-set entries vs Redis 8.0 (Momento benchmark, independent). Drop-in replacement for Redis 7.2 workloads. AWS ElastiCache and Google Memorystore now both default to Valkey for new deployments.
The Redis license timeline (2009-2026)
The license saga is the deciding factor for many 2026 teams. 7 events, sourced.
Benchmark snapshot (2024-2026, sourced)
Every number labelled vendor-sourced or independent. Full data on /benchmarks.
| Workload | Winner | Delta | Source type |
|---|---|---|---|
| Simple GET/SET, high concurrency | Memcached | ~20-25% throughput edge | Independent |
| Batched 10-op pipeline | Redis | ~7% edge (800k vs 750k ops/sec) | Independent |
| Memory at 50M sorted-set entries | Valkey 8.1 | 28% lower (3.77 GB vs 4.83 GB) | Independent |
| Multi-threaded I/O | Valkey 8.0 | 30-35% throughput gain | Independent |
| Valkey 8.0 vs 7.2 RPS | Valkey 8.0 | 230% improvement (vendor claim) | Vendor |
| Redis 8.0 latency improvements | Redis 8.0 | Up to 78% bitmap latency | Vendor |
Source: DevGenius March 2026 (AWS c6i.2xlarge), Momento (AWS c8g.2xlarge Graviton4), Valkey blog (AWS c7g.4xlarge Graviton3). Vendor-sourced numbers labelled; replicate with your workload before committing.
Use cases: who wins what
Real-world named users (Facebook / Memcached, Twitter / Redis, Aiven / Valkey). Full matrix at /use-cases.
Sessions need persistence + replication. Memcached restart wipes all sessions. Redis RDB/AOF + master-replica = safe sessions. Valkey works equally well.
Multi-threaded, ~20-25% throughput edge on simple GET/SET (DevGenius 2026). Lower per-item memory overhead. Simple by design. Facebook runs the world's largest Memcached deployment.
Memcached has no pub/sub. Redis SUBSCRIBE/PUBLISH fire-and-forget, or Redis Streams for persistent consumer groups. Valkey supports both equivalently.
Frequently asked questions
Is Redis better than Memcached?⌄
Better at different things. Memcached wins on raw GET/SET throughput at high concurrency (DevGenius 2026: ~20-25% edge, AWS c6i.2xlarge) and lower per-item memory overhead. Redis wins on data types, persistence, replication, pub/sub, clustering, and security. For 80%+ of new projects in 2026, Redis or Valkey is the right call. The Memcached lane is real but narrow: simple ephemeral page caching, no persistence requirement, no structured data.
Is Redis still open source in 2026?⌄
Partially. After the March 2024 SSPL/RSALv2 switch, the OSI did not recognise Redis as open source. May 2025 added AGPLv3 as a third option (tri-license). AGPLv3 is OSI-approved open source, but its network copyleft ("if you run a modified version as a service, you must publish the source") is uncomfortable for many commercial products. Valkey remains BSD-3 permissive with no strings. Memcached has always been BSD.
Should I migrate from Redis to Valkey?⌄
If your license review flags SSPL or AGPLv3 as a problem, yes. Valkey is a drop-in replacement for Redis 7.2.4 baseline commands and is fully RESP-compatible. If you need Redis 8.0 features (vector sets, hash field TTL) that Valkey has not yet shipped, stay on Redis. If you are on AWS ElastiCache or Google Memorystore, check whether you are already on Valkey by default (likely yes for new clusters since late 2024). See the full guide at /valkey-vs-redis.
Related engineering decisions
Polyglot teams making cache decisions are often making repo layout decisions too.
Redis clients differ in Rust vs Go ergonomics. Language and cache layer decisions are linked.
Migrating to Valkey in CI/CD staging compounds test run costs. Calculate the real cost.
Cache layer choice is one node in the broader stack-cost question.