distributed key-value storage / caching
Valkey is a high-performance, Redis-compatible distributed key-value database and data structure server optimized for caching and real-time workloads.
Same problem, same approach. Swapping one for another is a config change, not a rewrite.
choose when you want a C++-based Redis-compatible server from an open-source foundation, with active development and a permissive BSD license.
Pikiwidb is a Redis-Compatible database developed by Qihoo's infrastructure team.
choose when you prefer the original Redis with the largest ecosystem and newest features, but can accept its non-permissive license.
For developers, who are building real-time data-driven applications, Redis is the preferred, fastest, and most feature-rich cache, data structure server, and document and vector query engine.
Solves the same problem with a different architecture or at a different layer. Expect to rewrite the integration.
choose when you need higher throughput on many cores via a multi-threaded shared-nothing architecture that replaces Redis and Memcached.
A modern replacement for Redis and Memcached
choose when you want a .NET-based high-performance remote cache-store with Redis protocol support, especially for Windows-centric deployments.
Garnet is a remote cache-store from Microsoft Research that offers strong performance (throughput and latency), scalability, storage, recovery, cluster sharding, key migration, and replication features. Garnet can work with existing Redis clients.
choose when you need a Java in-memory data grid with stream processing and a broader data platform rather than a pure key-value cache.
Hazelcast is a unified real-time data platform combining stream processing with a fast data store, allowing customers to act instantly on data-in-motion for real-time insights.
choose when you want a Go-native distributed cache that can be embedded as a library or run as a standalone service.
Distributed, in-memory key/value store and cache. It can be used as an embedded Go library and a language-independent service.
choose when you need Redis protocol compatibility with a distributed transactional backend on TiKV, despite its stale maintenance.
Distributed transactional NoSQL database, Redis protocol compatible using tikv as backend
These projects were analysed and named valkey among their alternatives. The relationship is not symmetric — how valkey rates them is a separate judgement, made when valkey is analysed in its own right.
calls valkey “community-driven Redis fork, drop-in replacement; choose for Redis compatibility with active development”
A modern replacement for Redis and Memcached
calls valkey “Community-maintained fork of Redis, choose if you prefer a vendor-neutral, actively developed Redis-compatible server with a focus on long-term OSS.”
A Multithreaded Fork of Redis
calls valkey “choose for a community-maintained Redis-compatible cache with battle-tested C code and the open Redis ecosystem”
Garnet is a remote cache-store from Microsoft Research that offers strong performance (throughput and latency), scalability, storage, recovery, cluster sharding, key migration, and replication features. Garnet can work with existing Redis clients.
calls valkey “Choose it when you want an actively maintained community Redis fork with the same in-memory architecture and Redis protocol.”
SSDB - A fast NoSQL database, an alternative to Redis
calls valkey “choose when you want a BSD-licensed Redis-compatible key-value store/cache and no Hazelcast-style compute or stream processing.”
Hazelcast is a unified real-time data platform combining stream processing with a fast data store, allowing customers to act instantly on data-in-motion for real-time insights.