“"Valkey is not behaving like most forks and declining in interest, commits and project traction. Instead, it seems to have found a level of sustainable development velocity that shows no signs of stagnation, one enabled by a relatively diverse set of project backers." — Stephen ...”
You know that feeling when a core piece of your infrastructure changes its license overnight? Redis Inc. switched Redis from MIT to SSPL/RSALv2 in March 2024 — cloud providers and SaaS companies could no longer offer Redis-compatible services without licensing fees or open-sourcing their entire stack. At the same time, Redis 7.2's single-threaded architecture leaves CPU cores idle under heavy I/O: on a 16-vCPU machine you get the throughput of one thread while 15 sit unused. Valkey solves both: a permissive BSD-3-Clause license that cannot be revoked, and an I/O threading model that reaches 1.19M RPS on the same hardware where Redis 7.2 tops out at 360K.
Valkey keeps Redis's core design: every command runs on a single thread so operations are atomic with no locks or race conditions. On top of that, Valkey 8.0 added a pool of async I/O threads (configured with --io-threads N) that handle all network reads and writes in parallel. Think of it like a restaurant where one chef still controls the kitchen — guaranteeing no two orders conflict — but now 8 runners carry food to tables simultaneously instead of one runner doing all the trips. You point your existing Redis client at Valkey's port and nothing else changes — same commands, same response format, same config file syntax.
If you run Redis 7.2 in production and want out of the SSPL licensing conversation, Valkey is a direct path — swap the binary, enable I/O threading, and the migration is done in hours. If you are hitting 200–400K RPS on a multi-core instance while cores sit idle, adding --io-threads 8 gives you the equivalent of 3× the hardware at zero cost. This is NOT the right move if you have already upgraded to Redis 7.4+ — the dump file format changed, and migrating back requires third-party tooling that adds risk.
Yes, if you are on Redis 7.2.x — this is a straightforward swap with verified production adoption at AWS scale. The 37% throughput gain and 60%+ p99 latency improvement versus Redis 8.0 come from an independent Momento benchmark, not Valkey's own numbers. Hold off if you depend on Redis 7.4+ dump files or if your workload runs CPU-intensive sorted-set commands, where DragonflyDB's sharded model outperforms Valkey by 29× at 48 vCPUs per DragonflyDB's own benchmark.
Deep-dive insight, Easy and Pro modes, plus action playbooks — the full breakdown is one tap away.