Discofork
Repository brief

dragonflydb/dragonfly

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T15:39:33.220Z
1mo ago

dragonflydb/dragonfly

Dragonfly is an actively maintained, high-profile open source in-memory data store positioned as a modern replacement for Redis and Memcached. It is large and mature, with strong adoption signals (30k+ stars, 1.1k+ forks) and very recent activity on March 30, 2026. Forks are likely interesting if you care about performance-oriented distributed cache/database infrastructure, Redis/Memcached compatibility, or systems work in C++ with supporting Python tooling and documentation.

GitHub
Loading tags...
Stars30,266
Forks1,164
Default branchmain
Last pushed2026-03-30T15:28:14Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Choose upstream unless you specifically need this exact snapshot; the fork adds no visible value and is slightly behind.

Prefer upstream unless you specifically need the fork's Bloom-filter/SBF experiments or other local customizations and are willing to absorb major maintenance and rebase cost. This fork is not a good choice for users who want current upstream compatibility, broad platform support, or low operational risk.

Prefer this fork only if its specific customizations are the point. If you want an actively maintained Dragonfly with the latest fixes and predictable compatibility, upstream is the safer choice.

Choose this fork only if you need its specific local fixes or are maintaining an existing deployment on top of it. For new adopters, upstream Dragonfly is the better default because this fork is materially stale and significantly diverged.

Prefer upstream unless you explicitly need this fork's custom behavior or legacy baseline. This fork looks too stale and too divergent for a low-risk production adoption path.

Prefer upstream unless you specifically need this fork's old custom replication/testing behavior. For new adopters, the fork looks too stale and too divergent to be a safe default choice.

Prefer upstream unless you specifically need this fork's old behavior or its small set of custom admin workflows. For new adoption, the drift and staleness make it a poor base.

Prefer upstream unless you specifically need this exact snapshot. This fork adds no visible capabilities and is already behind on recent fixes and features, so it is not a good adoption target for production or active development.

Choose upstream instead unless you specifically need this exact older snapshot. The fork has no unique additions and is behind on recent fixes and features, so its main value is as a temporary pinned baseline.

Prefer this fork only if you specifically need its custom changes and are willing to own a large divergence from upstream. For most adopters, upstream Dragonfly is the safer choice because this fork is materially behind and appears to have removed or rewritten significant core areas.