Redis vs Memcached vs Valkey: Frequently Asked Questions (2026)

Better at different things. Memcached wins on raw GET/SET throughput at high concurrency (~20-25% edge, DevGenius March 2026, independent benchmark, 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 or structured-data requirement.

It is not always faster. It depends on workload. Memcached's multi-threaded architecture wins at high concurrency on simple GET/SET operations (DevGenius 2026: ~250k vs ~180k GET ops/sec, 256-byte values, 128 concurrent connections). Redis's pipelining and complex data type commands win on batched and structured operations (DevGenius 2026: ~800k vs ~750k batched 10-op pipeline ops/sec). The 'faster' question requires specifying: at what operation, at what concurrency, on what hardware.

Partially. After the March 2024 SSPL switch, the OSI no longer recognised Redis as open source. May 2025 added AGPLv3 as a third option alongside SSPLv1 and RSALv2 (tri-license). AGPLv3 is OSI-approved open source, making Redis OSI-compliant again for the first time since March 2024. But AGPLv3's network copyleft (if you run a modified Redis as a service, you must publish source) is uncomfortable for many commercial products. Valkey (BSD-3-Clause) is the fully unrestricted option. Memcached has always been BSD.

Linux Foundation fork of Redis 7.2.4 BSD, launched April 2024 when Redis dropped BSD for SSPLv1 + RSALv2. Backed by AWS, Google Cloud, Oracle, and Ericsson. Drop-in replacement for Redis 7.2 commands (RESP-compatible). Valkey 8.1 (early 2026) adds ~28% memory efficiency improvement at 50M sorted-set entries vs Redis 8.0 (Momento benchmark, independent) and 30-35% multi-threaded I/O throughput improvement. AWS ElastiCache and Google Memorystore both default to Valkey for new deployments.

No. Process restart wipes all Memcached data. By design: Memcached is a cache, not a database. If you need persistence (sessions, rate-limit counters, anything you cannot regenerate), use Redis or Valkey. Redis and Valkey both offer RDB snapshots (point-in-time) and AOF write-ahead logs (full durability).

Redis or Valkey for sessions. Memcached for sessions is a known footgun: (1) no persistence means a process restart logs out all users; (2) no replication means a single node failure = session loss; (3) LRU-only eviction can evict active sessions under memory pressure; (4) no atomic field updates makes session updates race-prone. Redis and Valkey solve all four problems. Rails 7+, Django, and express-session all steer toward Redis as the default session store.

No. Memcached is a key-value cache only. For pub/sub use Redis (SUBSCRIBE/PUBLISH, fire-and-forget), Redis Streams (XADD/XREAD/XGROUP, persistent with consumer groups), Valkey (equivalent to Redis 7.2 baseline for both), or a dedicated message broker (Kafka for cross-DC durability, NATS for high-throughput lightweight pub/sub, RabbitMQ for complex routing).

No. Memcached 1.6.x is actively maintained in 2026. Released in 2003, BSD-licensed, never changed license. Used in production by Facebook (world's largest Memcached deployment, documented in NSDI 2013 'Scaling Memcache at Facebook'), Wikipedia, YouTube, Twitter (legacy). Less hyped than Redis since 2010, but not deprecated. Its lane is narrow (pure ephemeral cache, multi-threaded throughput), but within that lane it is the right tool.

AWS backed the Valkey fork (April 2024, Linux Foundation) because Redis's SSPLv1 and RSALv2 licenses make the managed-service business model legally fraught. SSPLv1 specifically targets managed-service providers: if you offer SSPL software as a service, you must open-source your entire stack. AWS, Google Cloud, Oracle, and Ericsson co-founded the Valkey project under the Linux Foundation. Valkey's BSD license removes the license risk for managed-service providers. AWS migrated ElastiCache defaults to Valkey in late 2024.

Yes, free to use. But 'free' and 'open source' are different. Redis 8.0 is tri-licensed: RSALv2 (source-available, restricts managed-service competition with Redis Inc), SSPLv1 (source-available, requires open-sourcing your stack if you offer Redis as a managed service), and AGPLv3 (OSI-approved open source, copyleft). For internal use: any license works. For SaaS products using Redis internally: AGPLv3 copyleft may be problematic. For offering Redis as a managed service: SSPL and RSALv2 directly restrict this. Valkey (BSD) has none of these strings.

Facebook (largest Memcached deployment in the world, documented in NSDI 2013 'Scaling Memcache at Facebook' by Nishtala et al.; Facebook has moved some workloads to their own in-memory systems but Memcached remains in use), Wikipedia, YouTube, Twitter (legacy, before their own in-memory infrastructure), Reddit (early days), Tumblr, LiveJournal. The common pattern at scale: Memcached for HTML page caching, Redis for everything requiring data structures or persistence.

If your license review flags SSPL or AGPLv3 as a problem, or if you are on AWS/GCP managed and want the default path: yes. Valkey is a drop-in replacement for Redis 7.2.4 commands (RESP-compatible). Most Redis clients (ioredis, redis-py, Jedis) work with Valkey unchanged. If you need Redis 8.0-specific features (vector sets, hash field TTL): stay on Redis, Valkey has not shipped those yet. If you are on AWS ElastiCache, check if your cluster is already on Valkey by default (likely for new clusters created since late 2024).

It works in 2026 and is BSD-licensed (the last BSD Redis release). The problem is security patches: community backports to 7.2.4 are not guaranteed past 2026-2027. Running frozen Redis 7.2.4 as a 'license dodge' accumulates tech debt: any CVE in Redis 8.x may or may not get a 7.2.4 backport. Valkey is the intended open-source successor to the Redis 7.2 baseline. If you want BSD-clean and maintained, migrate to Valkey rather than freezing on 7.2.4.

Redis Source Available License v2. A source-available license written by Redis Inc. Not OSI-approved. The key restriction: you cannot provide a managed-service offering of Redis to third parties (i.e., you cannot be AWS ElastiCache for Redis) without a commercial agreement with Redis Inc. RSALv2 does not restrict most internal uses of Redis, but it makes it impossible for cloud providers to offer managed Redis without a deal with Redis Inc. This is why AWS and Google backed the Valkey fork.

Not as of early 2026. Redis 8.0 (May 2025) introduced vector sets (VADD, VSIM commands, HNSW algorithm for approximate nearest neighbor search). This enables on-Redis vector similarity search for AI/RAG workloads. Valkey's roadmap includes vector search but it was not in Valkey 8.1. If your pipeline requires on-Redis vector similarity search in 2026, Redis 8.0 is required. DragonflyDB has its own vector search implementation.