DragonflyDB
Ranked 6 of 6 in-memory data stores by recommenders
A Redis-compatible in-memory database people run on a single VM and value for non-blocking snapshots. Critics report out-of-memory problems with large datasets and memory copying during snapshots.
A Redis-compatible in-memory database people run on a single VM and value for non-blocking snapshots. Critics report out-of-memory problems with large datasets and memory copying during snapshots.
6 people gave an opinion
- recommend it
- 5
- criticize it
- 1
- approval share
- 83%
Recommended in 5 of 13 months
- November 2025: recommended
- December 2025: not recommended
- January 2026: not recommended
- February 2026: recommended
- March 2026: not recommended
- April 2026: not recommended
- May 2026: recommended
- June 2026: recommended
- July 2026: not recommended
- August 2026: not recommended
- September 2026: not recommended
- October 2026: recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 5 people recommend itNeeds 10 or more, not met.
- 5 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 5 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Non-blocking snapshotting
“which is not an issue with dargonfly for it's non-blocking snapshotting”
Comment from 19 Oct 2026 in “Show HN: KiviDB, a faster Redis-compatible memory database and vector cache” Runs on a single VM
“But I just use dragonflydb on a single VM. No point paying for transactions.”
Comment from 3 Nov 2025 in “Oxy is Cloudflare's Rust-based next generation proxy framework (2023)” Named as a Redis alternative
“dragonfly, garnet, and pogocache are other alternatives too.”
Comment from 5 Feb 2026 in “It's 2026, Just Use Postgres”
What people warn about
Each mark is one comment
Out-of-memory crashes with large datasets
“OOM was a big one, because when we had large dataset for example 96G on a 126G dragonfly pod”
Comment from 19 Oct 2026 in “Show HN: KiviDB, a faster Redis-compatible memory database and vector cache” Snapshotting creates an in-memory copy
“it created a copy within its memory before storing it to the disk”
Comment from 19 Oct 2026 in “Show HN: KiviDB, a faster Redis-compatible memory database and vector cache”
Other in-memory data stores people recommend
The four most recommended other in-memory data stores, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| Redis | 174 | 102 | 63% | 12 | 10 yrs7 owners | — |
| Valkey | 31 | 5 | 86% | 10 | — | Approved |
| Memcached | 27 | 10 | 73% | 6 | — | Approved |
| Lux Redis-compatible server | 8 | 7 | 53% | 2 | — | — |
| DragonflyDBThis page | 5 | 1 | 83% | 5 | — | — |
What people said
6 of the 8 comments that mention it, newest first. Each links to the original comment.
“which is not an issue with dargonfly for it's non-blocking snapshotting”
“it created a copy within its memory before storing it to the disk”
“OOM was a big one, because when we had large dataset for example 96G on a 126G dragonfly pod”
“a good Dragonfly grammar should be something that keeps you at least up to par with your typing speed”
“dragonfly, garnet, and pogocache are other alternatives too.”
“But I just use dragonflydb on a single VM. No point paying for transactions.”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.