Redis-compatible key-value NoSQL database
SSDB is a disk-backed, Redis-protocol-compatible NoSQL database server supporting keys, hashes, zsets, and lists, built on LevelDB.
Same problem, same approach. Swapping one for another is a config change, not a rewrite.
Choose it when you want an actively developed Qihoo persistent Redis-compatible store backed by RocksDB.
Pikiwidb is a Redis-Compatible database developed by Qihoo's infrastructure team.
Choose it when you want an actively maintained Apache-governed RocksDB-backed Redis-compatible server.
Apache Kvrocks is a distributed key value NoSQL database that uses RocksDB as storage engine and is compatible with Redis protocol.
Choose it when you want a Tencent-maintained distributed persistent Redis-compatible store with cluster features.
Tendis is a high-performance distributed storage system fully compatible with the Redis protocol.
Solves the same problem with a different architecture or at a different layer. Expect to rewrite the integration.
Choose it when you need the canonical in-memory Redis feature set and ecosystem, accepting RAM cost instead of disk persistence.
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.
Choose it when you want an in-memory, multi-core-optimized Redis/Memcached-compatible server and can keep data in RAM.
A modern replacement for Redis and Memcached
Choose it when you want an actively maintained community Redis fork with the same in-memory architecture and Redis protocol.
A flexible distributed key-value database that is optimized for caching and other realtime workloads.
Choose it when you want a C#/.NET cache-store speaking Redis/Memcached protocols with strong throughput.
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 it when you need a distributed, transactional NoSQL database using TiKV with Redis protocol, despite its incubator/unmaintained state.
A distributed transactional large-scale NoSQL database powered by TiKV
Choose it when you want a distributed transactional TiKV-backed Redis-protocol database, though it is no longer updated.
Distributed transactional NoSQL database, Redis protocol compatible using tikv as backend
Choose it when you want a Seastar-based high-concurrency Redis-compatible store, despite being old and unmaintained.
NoSQL data store using the SEASTAR framework, compatible with Redis
Choose it when you need a distributed Redis-protocol compatible NoSQL database, though it is stale.
A Distributed Redis Protocol Compatible NoSQL Database
An earlier or more limited way to do the job. Still the right call when you need something small, proven, or CPU-only.
Choose it when you need a formerly maintained persistent Redis-protocol server with pluggable storage engines like LevelDB/RocksDB/LMDB.
A redis protocol compatible nosql, it support multiple storage engines as backend like Google's LevelDB, Facebook's RocksDB, OpenLDAP's LMDB, PerconaFT, WiredTiger, ForestDB.
Choose it when you prefer a Go-based persistent Redis-compatible server, accepting stale maintenance.
A high performance NoSQL Database Server powered by Go
Choose it when you need only a simple key-value Redis-protocol store backed by Postgres and can accept missing collection data types.
a very simple pure key => value storage system that speaks Redis protocol with Postgres as storage engine and more
These projects were analysed and named ssdb among their alternatives. The relationship is not symmetric — how ssdb rates them is a separate judgement, made when ssdb is analysed in its own right.
calls ssdb “Disk-backed key-value store with Redis-compatible API, choose when your workload exceeds RAM and you need a more persistent storage engine instead of pure in-memory.”
A Multithreaded Fork of Redis