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 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM 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

37 sources
Great blog with a lot of good stuff. Loved their Scalable In Memory Dragonfly Swarm post, for example. https://www.dragonflydb.io/blog/announcing-dragonfly-swarm-s... I do wish they did more to show folks how to go deeper in integrating Dragonfly. A readme update 2 years ago talked about a native distributed log that would offer super fast option for integrators. That's the sort of super neat stuff that will entice geeks to come play: not just redis but faster, but having a deeper connection to the machine, to seeing what else is possible. https://github.com/dragonflydb/dragonfly/blame/main/README.m...
In Dragonfly: Modern Replacement for Redis and Memcached
I used to run it on a 4 core Celeron NUC with a measly 8 gig of ram and 1 TB SSD via the community fpm container: https://github.com/nextcloud/docker I now run it on a much more powerful system but performance wise it's the same. Side containers DB: I use postgres Redis: https://github.com/dragonflydb/dragonfly as the redis container Image processing: imaginary container maintained by the Nextcloud team Most of this is available in the AIO setup but I prefer manually tuning things for my system As it's a __big__ SAS product to run it well on lower end systems you MUST: - Tune your PHP settings to your system. - Tune your DB settings - Set up caching properly - Offload as much processing as possible to background processes (e.g. preview generation) Probably tune your Proxy settings as well. Big changes I've made: - Switch logging to error
Read the rest
only and syslog (not the normal file on disk) as it can hammer single disk systems. - Switch to unix sockets for redis and the database for quite a performance boost.
In OpenCloud 1.0
I recently ran across the the license for Dragonfly [1] which has some restrictions (rights reserved), but 5 years after the license date the license switches to Apache 2.0. Basically a time-limited rights reservation. I don't hate it. I might even contribute to such a project for free. I propose something like this: When I release code, it's rights-reserved for 5 years, then open-source (and this particular clause would be irrevocable). Anyone may use the software for non-commercial purposes. Anyone may contribute, those who contribute will be granted permission for commercial use if I deem their contributions significant enough. Anyone may distribute the software under these terms. If such a model became popular, I have a hard time imagining it could make things any worse. It might even accelerate open-source development by shifting soc
Read the rest
ieties resources to those who are actually producing this valuable software. You might say, "but it's not open-source", fair enough, but we can view it as open-source contribution with a delay. For example, if this model became widely popular this year, and we saw great progress with this model, then come 2028 we would be flooded with new open-source software and ultimately might be better off than we would have been without this model. Ultimately people choose to make their software open-source for moral reasons, and because they hope that by giving they might receive in turn--I contribute, you contribute, and we share freely (and we're both poor). This model I've talked about still achieves similar goals. People might still be willing to contribute, even for free, because I have given them an irrevocable legal promise that their contributions will be made available to all at a specific time. (This whole thing makes me rethink copyright and patents and how much they really contribute to society. Perhaps their terms should be shortened?) [1]: https://github.com/dragonflydb/dragonfly/blob/main/LICENSE.m...
In Generating Income from Open Source
1. We removed the FAQ page 2. You are right, I need to shut the fuck up and let self-righteous hn crowd with torches do what they do best - find a weakness, and push it until they get bored and switch to beat another builder. You asked me about my perspectives and priorities? These are my priorities: https://github.com/dragonflydb/dragonfly/graphs/contributors 3. The first thing I did was on this thread was to apologize for having FAQ with such content.
In Dragonfly – Performant in-memory data store
hmm and ships are designed to sail, yet you use planes to cross atlantic. Nokia was designed as strongest and most affordable phone, yet you use Iphone that costs 1000$. it's not about how it was designed but whether it addresses your current needs. Developers do not want to manage a cluster of single cpu processes. Not on their laptops and not in the production. And it's not just about management complexity. See this https://github.com/dragonflydb/dragonfly/issues/1229 and it's just one example. Single cpu - is just not enough for today use-cases.
In Dragonfly – Performant in-memory data store

Showing the 15 most recent of 37 sources. Enable JavaScript to search and browse every indexed mention.

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.