Comparison · Database
Valkey vs Dragonfly: Redis replacement comparison
Two ways out of Redis’s source-available licence — the LF-backed fork (Valkey) and the multi-threaded rewrite (Dragonfly).
See also: Redis vs ValkeyDatabase news
The headline difference
Valkey is the Linux-Foundation-hosted, BSD-licensed fork of Redis. Dragonfly is a purpose-built, multi-threaded Redis-compatible store written in C++. Valkey optimises for behavioural compatibility; Dragonfly optimises for per-core throughput.
Architecture comparison
| Dimension | Valkey | Dragonfly |
|---|---|---|
| Threading | Single-threaded (Redis lineage) | Multi-threaded shard-per-thread |
| License | BSD (LF-hosted) | BSL (source-available) |
| Wire compatibility | Full RESP3 | Full RESP3 |
| Memory efficiency | Redis-equivalent | ~30% better in dense workloads |
| Throughput on 32 cores | ~1x Redis baseline | ~25x Redis baseline |
| Backed by | AWS, Google, Oracle, Ericsson | Dragonfly Inc |
When Valkey wins
You want the safest possible Redis migration. Valkey is a binary-compatible drop-in for Redis 7.2.4. Same config, same client libraries, same operational playbook.
You’re a cloud provider. The major hyperscalers backed Valkey precisely to have a permissively-licensed Redis-equivalent they can offer as a managed service.
When Dragonfly wins
You’re CPU-bound on Redis. If single-thread Redis is your throughput bottleneck and your workload fits Dragonfly’s strong commands (GET/SET, HSET/HGET, simple JSON), the throughput gain is dramatic.
You want lower TCO at scale. Fewer larger Dragonfly instances replace many small Redis instances, simplifying ops and reducing infrastructure cost.
Frequently asked questions
Is Valkey or Dragonfly the better Redis replacement?
Valkey is the closest behavioural drop-in — it forked from Redis 7.2.4 BSD and preserves the protocol and feature set. Dragonfly is faster but architecturally different (multi-threaded, shard-per-thread); you’ll see meaningful gains on multi-core hardware but should test the specific commands your application uses.
How fast is Dragonfly compared to Redis?
Dragonfly benchmarks 25x throughput on a 32-core box compared to single-threaded Redis. Real-world gains depend heavily on workload — GET/SET-heavy workloads see the biggest win; LIST/SET/HASH operations less so.
Does Valkey support Redis modules?
Yes for the BSD-licensed core; no for Redis Stack modules (RedisJSON, RedisSearch, etc.) which Redis Inc retained under the source-available SSPL. The Valkey project is building replacements as community modules.
Should I migrate from Redis to Dragonfly?
If you’re bottlenecked on CPU and your workload is read-heavy with simple data types, yes — the throughput jump is real. If you use Redis Streams, Pub/Sub at high scale, or Lua scripts, test carefully — Dragonfly’s implementations are not bit-identical.
What about backup, replication, persistence?
Valkey replicates Redis behaviour 1:1 — AOF, RDB, replica chains, Sentinel all work as-is. Dragonfly supports BGSAVE-style snapshots and a unique replication mode, but Sentinel and Redis Cluster are not yet feature-complete.