AltHub

dragonflydb/dragonfly Alternatives

in-memory data store / Redis-compatible cache

Dragonfly is an in-memory data store compatible with Redis and Memcached, designed for high throughput and low latency.

31.0kC++NOASSERTIONactive · last push 1mo agoGitHub

Drop-in peers

Same problem, same approach. Swapping one for another is a config change, not a rewrite.

microsoft/garnetGitHub

Redis-compatible remote cache-store with high performance; choose if you prefer a C# implementation and need a drop-in Redis replacement

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.

12.0k
C#
MIT
active1mo ago
valkey-io/valkeyGitHub

community-driven Redis fork, drop-in replacement; choose for Redis compatibility with active development

A flexible distributed key-value database that is optimized for caching and other realtime workloads.

27.0k
C
BSD-3-Clause
active1mo ago
OpenAtomFoundation/pikiwidbGitHub

Redis-compatible database, active; choose if you want a similar drop-in replacement from Qihoo

Pikiwidb is a Redis-Compatible database developed by Qihoo's infrastructure team.

6.1k
C++
BSD-3-Clause
active2mo ago

Older generation, or narrower

An earlier or more limited way to do the job. Still the right call when you need something small, proven, or CPU-only.

Snapchat/KeyDBGitHub

multithreaded Redis fork that inspired Dragonfly, but stale; use if you need a feature set similar to Dragonfly and don't mind unmaintained code

A Multithreaded Fork of Redis

12.5k
C++
BSD-3-Clause
dormant2.4y ago

Listed as an alternative to

These projects were analysed and named dragonfly among their alternatives. The relationship is not symmetric — how dragonfly rates them is a separate judgement, made when dragonfly is analysed in its own right.

redis/redisGitHub

calls dragonfly “Choose when you need higher multi-threaded throughput while keeping the Redis protocol.”

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.

76.1kCactive
Snapchat/KeyDBGitHub

calls dragonfly “Redis-compatible server built from scratch for high throughput and memory efficiency, choose when you want a modern C++ implementation independent of Redis fork tree.”

A Multithreaded Fork of Redis

12.5kC++dormant
microsoft/garnetGitHub

calls dragonfly “choose for a C++-based Redis/Memcached-compatible server with high throughput and lower memory when you don't need .NET”

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.

12.0kC#active
valkey-io/valkeyGitHub

calls dragonfly “choose when you need higher throughput on many cores via a multi-threaded shared-nothing architecture that replaces Redis and Memcached.”

A flexible distributed key-value database that is optimized for caching and other realtime workloads.

27.0kCactive
ideawu/ssdbGitHub

calls dragonfly “Choose it when you want an in-memory, multi-core-optimized Redis/Memcached-compatible server and can keep data in RAM.”

SSDB - A fast NoSQL database, an alternative to Redis

8.3kC++dormant
hazelcast/hazelcastGitHub

calls dragonfly “choose when Redis/Memcached-protocol high-throughput caching is all you need and you do not need Hazelcast's JVM data grid 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.

6.6kJavaactive