Redis vs Memcached vs Valkey in 2026
The classic Redis-vs-Memcached choice became a three-way one when the Linux Foundation forked Valkey from Redis in April 2024. Valkey now carries the Redis feature set under a permissive license, which changes the answer for most teams. Here is the whole decision in one table, with the specific cases where each engine still wins.
Why this is now a three-way choice
For over a decade the in-memory decision was binary: Memcached for a fast, dumb cache, or Redis when you needed data structures and persistence. That changed in March 2024, when Redis Inc replaced the BSD license with SSPLv1 and RSALv2, later adding AGPLv3 in May 2025. See the full license timeline for the sequence.
The relicensing pushed AWS, Google, Oracle, and Ericsson to launch Valkey, a Linux Foundation fork of Redis 7.2.4 that keeps the Redis feature set under a permissive BSD license. Within months the major clouds defaulted their managed services to it. So the practical field is now three engines, not two: a minimal cache (Memcached), a full-featured BSD store (Valkey), and the newly-licensed original (Redis 8) that adds core vector sets and folds in the proprietary Redis Stack modules.
The consequence for most teams is that Valkey absorbed the reason to reach for Redis. If you wanted Redis for its data structures and durability but not its license, Valkey gives you the first without the second. That leaves Memcached and Redis 8 each defending a narrower, sharper case, which is what the rest of this page lays out.
Redis 8 vs Memcached 1.6 vs Valkey 9.1: side-by-side
| Feature | Redis 8 | Memcached | Valkey |
|---|---|---|---|
| License | SSPLv1 / RSALv2 / AGPLv3 (source-available; AGPLv3 is OSI) | BSD-3-Clause (permissive, OSI) | BSD-3-Clause (permissive, OSI) |
| Origin | Redis Inc, 2009; relicensed 2024 | Danga Interactive, 2003 | Linux Foundation fork of Redis 7.2.4, Apr 2024 |
| Data model | Strings, hashes, lists, sets, sorted sets, streams, bitmaps, HLL, geo, vector sets | Strings only (opaque key-value) | Same as Redis 7.2 set (strings, hashes, lists, sets, sorted sets, streams, bitmaps, HLL, geo) |
| Persistence | RDB + AOF | None (pure in-memory) | RDB + AOF |
| Replication / clustering | Yes (primary-replica + cluster) | None (client-side sharding) | Yes (primary-replica + cluster) |
| Threading | Multi-threaded I/O | Multithreaded since 2003 | Multi-threaded I/O (redesigned 8.0) |
| Pure GET/SET throughput | Fast | ~20-25% faster at high concurrency | Fast |
| Vector / similarity search | Core vector sets (VADD/VSIM), Redis 8.0 | No | valkey-search module (GA Jul 2025); not a core type |
| Proprietary modules | Redis Stack (RedisJSON, RediSearch) built in | No | Own module ecosystem; not RedisJSON/RediSearch |
| Current version | 8.10 (July 2026) | 1.6.x | 9.1 (May 2026) |
| AWS ElastiCache | Redis OSS frozen at 7.1 (Nov 2023) | For Memcached (own engine) | Default engine; ~20% cheaper per node |
| GCP Memorystore | For Redis (Redis OSS) | For Memcached | For Valkey (default for new) |
Sources: redis.io, valkey.io, memcached wiki. Throughput edge per this site's benchmark page; managed-engine details on cloud Valkey support.
Which one, and when
Valkey
- You want the full Redis data-structure and persistence feature set under a clean, permissive BSD license with no SSPL or AGPLv3 strings.
- You are provisioning managed cache on AWS ElastiCache or Google Memorystore, where Valkey is the default engine for new clusters and priced about 20% below Redis OSS.
- You are migrating off Redis 7.2 and want the closest drop-in that keeps getting maintained and updated.
Memcached
- Your workload is a pure ephemeral cache of opaque string values and never needs a data structure, persistence, or replication.
- Raw GET/SET throughput per dollar at high concurrency is the single deciding metric; Memcached holds a ~20-25% edge on that benchmark.
- You want the simplest operational model: no cluster protocol, no failover to reason about, scale out by adding stateless nodes.
Redis 8
- You specifically need the core vector set data type (VADD/VSIM) as a first-class type rather than a loadable module.
- You depend on the proprietary Redis Stack modules (RedisJSON, RediSearch) whose behaviour Valkey does not match one-for-one.
- You hold a commercial Redis Cloud SLA and accept the SSPL/RSAL/AGPLv3 licensing that comes with Redis 8 and later.
The three pairwise decisions, in detail
Once you have narrowed the field, each pair has its own decision page. Redis vs Memcached is the classic caching-tier question of a rich store versus a minimal one. Valkey vs Redis is almost entirely a license-and-roadmap question, since Valkey matches the Redis 7.2 feature set and Redis 8 adds core vector sets on top. Valkey vs Memcached is the cleanest technical comparison of the three, because both are BSD-licensed and the license drama drops out entirely.
If you are choosing a managed service rather than self-hosting, the decision often collapses further: on AWS ElastiCache the Redis OSS engine is frozen at 7.1 and every newer engine version is Valkey, so the real managed contest is Valkey vs Redis OSS on ElastiCache and Valkey vs Memcached. Google Memorystore offers all three as separate services; see GCP Memorystore.
FAQ
Redis vs Memcached vs Valkey: which should I choose in 2026?
Start with Valkey. It is the BSD-licensed Linux Foundation fork of Redis 7.2.4, carries the full Redis data-structure and persistence feature set, and is the default engine for new clusters on AWS ElastiCache and Google Memorystore, where it is priced about 20 percent below Redis OSS. Choose Memcached instead when your workload is a pure ephemeral string cache and raw GET/SET throughput per dollar is the only thing that matters (it holds roughly a 20-25 percent edge on that narrow benchmark). Choose Redis 8 only when you specifically need its core vector set data type (VADD/VSIM) or the proprietary Redis Stack modules (RedisJSON, RediSearch), and you accept its SSPL/RSAL/AGPLv3 licensing.
Is Valkey the same as Redis?
Valkey is a fork of Redis 7.2.4, the last BSD-licensed Redis release, created in April 2024 after Redis Inc dropped the open-source BSD license. It speaks the same RESP protocol and matches the Redis 7.2 command set, so most Redis clients and workloads run on it unchanged. Since the fork the two have diverged: Valkey stays BSD and adds its own features (multi-threaded I/O redesign, hash field TTL in 9.0, the valkey-search module), while Redis 8 added core vector sets and folded in the formerly separate Redis Stack modules under SSPL, RSALv2, and AGPLv3.
Why do AWS and Google default to Valkey instead of Redis?
When Redis Inc replaced BSD with SSPLv1 and RSALv2 in March 2024, the managed-service business model became legally fraught, because SSPLv1 specifically targets providers that offer the software as a service. AWS, Google, and Oracle each run large managed in-memory services, so they co-founded the Linux Foundation Valkey fork to keep a permissive, RESP-compatible drop-in alive. Both clouds now default new deployments to Valkey. On ElastiCache the Redis OSS engine is frozen at 7.1 (November 2023) because AWS never shipped Redis 8.x, so every engine version from 7.2 upward is Valkey, not Redis.
Is Memcached still worth using over Redis or Valkey in 2026?
Yes, but for a narrower job than it used to hold. Memcached has been multithreaded since 2003 and its slab allocator does less bookkeeping per request, so on a pure GET/SET benchmark of small string values at high concurrency it still leads Redis and Valkey by roughly 20-25 percent. If your workload is genuinely a stateless cache of opaque blobs that never needs a data structure, persistence, or replication, Memcached does exactly that and nothing else, which keeps it fast and operationally simple. The moment you need counters, sorted sets, pub/sub, or durability, Memcached cannot do the job at all and the throughput comparison stops being apples-to-apples.
Does the Redis license change affect Memcached or Valkey?
No. The 2024-2025 Redis relicensing (SSPLv1, RSALv2, then AGPLv3) applies only to Redis 8 and later. Memcached has been BSD-3-Clause since 2003 and Valkey is BSD-3-Clause by design, so both are OSI-approved, permissive, and free of managed-service restrictions. If a procurement or legal review blocked Redis over SSPL or AGPLv3 copyleft, both Valkey and Memcached are clean on licensing grounds and the choice between them comes down purely to technical fit.
Can Valkey or Redis replace Memcached as a drop-in?
Functionally yes, but not wire-compatible. Memcached speaks its own text and binary protocols, while Redis and Valkey speak RESP, so switching means changing your client library from a memcached client to a Redis/Valkey client (redis-py, ioredis, Jedis, go-redis). Once migrated, either covers every Memcached use case and adds persistence and data structures. Going the other direction, from Redis to Valkey, is closer to a true drop-in because Valkey shares the Redis 7.2 command set and RESP protocol, and on ElastiCache the Redis OSS to Valkey engine upgrade is in-place with no endpoint change.