A
dragonfly
82.1
31,878 stars · license n/a
Databases
rocksdb leads by 8.8 · clear
A
82.1
31,878 stars · license n/a
B · leads
90.9
32,285 stars · GPL-2.0
dragonfly versus rocksdb is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in C++. The composite score is 82.1 for dragonfly and 90.9 for rocksdb.
rocksdb has 32,285 GitHub stars to dragonfly's 31,878, a gap of 407 (1.01×). Forks are 1,294 for dragonfly and 7,033 for rocksdb. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 81 versus 100.
Push history: dragonfly was last pushed on 17 November 2026 (0 days ago), and rocksdb was last pushed on 17 November 2026 (0 days ago). Open issues stand at 209 for dragonfly (0.007 per star) and 1,855 for rocksdb (0.057 per star). Issue-health scores are 84 and 52; activity scores are 100 and 100.
dragonfly is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. rocksdb is listed as GPL-2.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. License scores in this pair are 30 for dragonfly and 64 for rocksdb. This is a procurement signal, not legal advice.
Only rocksdb is marked self-hostable here (32,285 stars, deploy score 100). dragonfly is not (31,878 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: dragonfly is unpriced in this catalog, rocksdb is open source.
The lead is split. dragonfly is furthest ahead on issue health (84 to 52), while rocksdb is furthest ahead on self-hosting (100 to 35). Choose the dimension a rollout cannot compromise on.
rocksdb finishes ahead at 90.9 against dragonfly at 82.1, a 8.8 point clear margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | dragonfly | rocksdb |
|---|---|---|
| GitHub stars | 31,878 | 32,285 |
| Forks | 1,294 | 7,033 |
| Open issues | 209 | 1,855 |
| Adoption | 100 | 100 |
| Activity | 100 | 100 |
| Community | 81 | 100 |
| Issue health | 84 | 52 |
| License | 30 | 64 |
| Self-hosting | 35 | 100 |
| Composite | 82.1 | 90.9 |
A modern replacement for Redis and Memcached
A library that provides an embeddable, persistent key-value store for fast storage.
rocksdb has more GitHub stars: 32,285 versus 31,878 for dragonfly. The gap is 407 stars.
Both were last pushed on 17 November 2026.
Only rocksdb is marked self-hostable. dragonfly is not.
dragonfly is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. rocksdb is listed as GPL-2.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
rocksdb scores 90.9 and dragonfly scores 82.1. This page calls that a clear lead for rocksdb.