HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
dragonflydb
dragonfly
C++2022–2026
dragonflydb / dragonfly

dragonfly

A modern replacement for Redis and Memcached

29Distinct people
37Mentions
0Explicit recommenders
31.9KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A modern replacement for Redis and Memcached

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 12:01:57 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year37 dated mentions

Observed mentions: 2022-05-30 16:18:35 UTC to 2026-10-13 14:27:54 UTC.

0510152022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 14 mentions; 2 submissions, 12 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 14 mentions; 3 submissions, 11 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments20242025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC14212
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC14311
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC404
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC413
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

What Hacker News says

14 sources
I thought you'd never ask: - KeyDB (https://keydb.dev) - Pelican Cache (https://www.pelikan.io/) - Tendis (https://github.com/Tencent/Tendis) - SSDB (https://github.com/ideawu/ssdb) - Dynomite (https://github.com/Netflix/dynomite/) - Dragonfly (https://github.com/dragonflydb/dragonfly) - Skytable (https://github.com/skytable/skytable) - Tidis (https://github.com/yongman/tidis) - Anna (https://github.com/hydro-project/anna) - Skyhook (https://github.com/aerospike/skyhook) And some which are kinda dead but still interesting -- redis is the kind of workload that does actually become feature complete so these are still usable in my mind though maybe not first choice: - ledisdb (https://github.com/ledisdb/ledisdb) - Codis (https://github.com/CodisLabs/codis) - xcodis (https://github.com/ledisdb/xcodis) I'm planning on doing a comparison with t
Read the rest
hese at some point, because they're fascinating (all these projects go off in subtly different directions, I'll spare you the details), but here's a recent comparison someone else did: https://news.ycombinator.com/item?id=31796311 Basically, redis compatibility is like step 1 for any KVS that wants to seem at least a little usable/real-world-focused so you get so many cool entrants. I don't really personally keep up with redis for the stream use-case -- it's a great use for redis but that doesn't really make/break for me usually.
In I deleted 78% of my Redis container and it still works
johnwoods·Jun 19, 2022Submission

Redis vs. KeyDB vs. Dragonfly vs. Skytable

It seems that several projects claim that they have built the "world's fastest key/value store" or sometimes the phrase used is even more outrageous. The following projects are in question: - Redis: https://github.com/redis/redis - KeyDB: https://github.com/snapchat/keydb - Dragonfly: https://github.com/dragonflydb/dragonfly - Skytable: https://github.com/skytable/skytable And, these are my benchmark results (30 threads, 1 client per thread with GET/SET. See below for setup): 1. Redis: 112,100 / 99,892 2. KeyDB: 288,931 / 282,997 3. Dragonfly: 408,322 / 392,446 4. Skytable: 619,992 / 676,091 # Notes 1. Redis: I'll start with Redis which I'd like to call the "original" key/value store (after memcached) because it is the oldest and most widely used of all. Being a long-time follower of Redis, I do know it's single-threaded (and uses io-thre
Read the rest
ads since 6.0) and hence it achieves lesser throughput than the other stores listed above which are multi-threaded, at least to some extent. The best parts about Redis: it's the most feature complete of all the systems here, and is the oldest. (not saying old necessarily means better). 2. KeyDB: The second is KeyDB. IIRC, I saw it in a blog post which said that it is a "multithreaded fork of Redis that is 5X faster"[1]. I really liked the idea because I was previously running several instances of Redis on the same node and proxying them like a "single-node cluster." Why? To increase CPU utilization. A single KeyDB instance could replace the unwanted proxying funkiness, so I ditched Redis for KeyDB. Has been a fine experience so far, except for some occasional crashes. 3. Dragonfly: Just found it on HN and seems to be relatively new. Dragonfly claims that it is 25X faster (that I couldn't reproduce) than Redis[2] and has the slogan "Probably, the fastest in-memory store in the universe!". Doesn't support all the Redis commands yet, but I find it interesting mainly because of performance. Also, it's good to know why it is faster because it clearly outlines the underlying architecture[2]. The other three stores don't say much about it. Will be following the project. 4. Skytable: Found it while looking for projects written in Rust. Claims to be "insanely fast." Skytable's "experimental benchmarks" claim that it is something around 10X faster than Redis and some 2X-3X faster than KeyDB[3]. I hadn't heard of Skytable and it doesn't seem to be as widely used (unless I'm missing something?). I find it interesting because of the planned features[4] and performance. Only Skytable natively runs on Windows out of the four. Will be following the project. 5. My thoughts: Redis needs no introduction and is arguably super stable for use on production systems (using widely in our systems). KeyDB seems to be "stable enough" and it seems to be good for prod since Snapchat uses it already[5] (and so do we!). I found no Dragonfly v/s Skytable benchmarks. The best part about Redis, KeyDB and Skytable is that they don't make any "crazy assumptions" about the system they run on. What do I mean? Dragonfly expects you to have the latest hardware[6] and the latest kernel[7] on all your servers. I find this outrageous because not all servers run 5.10 and a majority of them are still using long-running branches on 4.x. Also, I don't expect them to have the latest processors, either. I'd argue if the other three stores started assuming the latest features, they'd be far faster than what they are today. Finally, both Dragonfly and Skytable are still early in their development so it may not be fair to compare their features against Redis and KeyDB who have been around for far longer. Also, all projects other than Skytable have companies behind them (unless I'm missing something). Edit #1: I have run the benchmarks myself for each store. In the benchmark with Redis, KeyDB and Skytable (redis-benchmark, memtier and sky-bench): Redis and KeyDB benchmarks seem to be very consistent, Skytable is a little inconsistent at times. However, in the benchmark with Redis, KeyDB and Dragonfly (with memtier), I was NOT able to reproduce the 25X speed that Dragonfly claims. I ran all tests on two m5.4xlarge servers (one with the k/v store and one with the benchmark tool). Edit #2: Added benchmark results What are your thoughts? Have you tried benchmarking any of them locally or in the cloud? References: [1]: https://docs.keydb.dev/blog/2019/10/07/blog-post [2]: https://github.com/dragonflydb/dragonfly [3]: https://github.com/ohsayan/sky-benches [4]: https://github.com/skytable/skytable/issues/203 [5]: https://docs.keydb.dev/news/2022/05/12/keydb-joins-snap [6]: https://github.com/dragonflydb/dragonfly/issues/124 [7]: https://github.com/dragonflydb/dragonfly/issues/96
130 points · Open discussion
Sorry, missed your second question. Redis is using fork-based save for snapshotting and full replica sync. This means that memory pages are duplicated on write. That consumes more memory than DF implementation that implements algorithmic point-in-time snapshotting. In addition DF was designed to use less overhead memory in its keys table. As for the why, you can read about it here: https://github.com/dragonflydb/dragonfly#background
In Dragonflydb – A modern replacement for Redis and Memcached
I want to take a minute to appreciate and recognize the https://github.com/dragonflydb/dragonfly#background section. A lot of projects say "faster" without giving some hint of the things they did to achieve this. "A novel fork-less snapshotting algorithm", "each thread would manage its own slice of dictionary data", and "core hashtable structure" are all important information that other projects often leave out.
In Dragonflydb – A modern replacement for Redis and Memcached

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.