Prometheus Alertmanager
Alertmanager is rebuilding its internals in the open, and 0.34 makes operators update their dashboards.
Comparison · Infra & APIs
Dragonfly vs nfs-ganesha
A side-by-side editorial comparison of Dragonfly and nfs-ganesha — release velocity, themes, recent moves, and the top alternatives to consider.
Dragonfly vs nfs-ganesha: at a glance
What is Dragonfly?
Dragonfly spends its releases on correctness in the parts of Redis compatibility nobody tests.
The visible window is almost entirely correctness and internals work on the 1.39/1.40 lines. The newest release consolidates two tiering knobs into a single tiered_max_pending_bytes and exports it to metrics. Behind it sit a memory-accounting backport, a cluster fix that journals FLUSHSLOTS from inside the flush transaction, and a HyperLogLog resync with valkey upstream that pulled in a CVE fix and exposed three Dragonfly-local bugs.
What is nfs-ganesha?
NFS-Ganesha is porting its management plane from DBUS to gRPC, four major versions in a month.
NFS-Ganesha is a user-space NFS server with pluggable FSAL backends for CEPH, GPFS and others. It is releasing major versions at an unusual rate — 12.0 through 15.1 since mid-July — and the connecting thread across all of them is gRPC: infrastructure first, then stats collection ported from DBUS, then more commands, then CacheMgr APIs and export management. Version 15.0 adds memory statistics and accounting alongside those APIs.
Dragonfly vs nfs-ganesha: editorial side-by-side
Dragonfly
5.0INFRA · APIS
Dragonfly spends its releases on correctness in the parts of Redis compatibility nobody tests.
◆ Current state
The visible window is almost entirely correctness and internals work on the 1.39/1.40 lines. The newest release consolidates two tiering knobs into a single tiered_max_pending_bytes and exports it to metrics. Behind it sit a memory-accounting backport, a cluster fix that journals FLUSHSLOTS from inside the flush transaction, and a HyperLogLog resync with valkey upstream that pulled in a CVE fix and exposed three Dragonfly-local bugs.
◆ Where it's heading
Two threads run through this window. One is upstream parity — the hyperloglog sync explicitly re-forks from valkey and keeps upstream formatting so future syncs stay cheap, which is a maintenance-cost decision as much as a correctness one. The other is the RESP IO loop v2 migration, visible in a pub/sub ordering fix gated on the v1 loop and in tests being skipped on the v1 leg of the regression matrix. Dragonfly is hardening a drop-in Redis replacement in the places where drop-in claims usually break: cluster operations, pub/sub ordering under pipelining, and memory accounting.
◆ Prediction
Expect continued RESP IO loop v2 work and more upstream syncs on forked Redis internals. The tiering flag consolidation plus its metrics export suggests tiered storage tuning is the next area to get operator-facing surface.
nfs-ganesha
6.3INFRA · APIS
NFS-Ganesha is porting its management plane from DBUS to gRPC, four major versions in a month.
◆ Current state
NFS-Ganesha is a user-space NFS server with pluggable FSAL backends for CEPH, GPFS and others. It is releasing major versions at an unusual rate — 12.0 through 15.1 since mid-July — and the connecting thread across all of them is gRPC: infrastructure first, then stats collection ported from DBUS, then more commands, then CacheMgr APIs and export management. Version 15.0 adds memory statistics and accounting alongside those APIs.
◆ Where it's heading
This is a control-plane migration carried out release by release in the open. Each version moves another slice of management surface onto gRPC — stats, exports, cache manager, a fake recall API for testing — while the data path work continues separately with XCOPY and clustered quality of service at 14.0. The 15.1 release extends ShowExports with a protocol summary and adds a gRPC FakeRecall API, which reads as filling in coverage rather than opening new ground. Note 15.0 and 15.1 are stamped seventy-nine seconds apart, so they were cut together rather than released as separate events.
◆ Prediction
Expect the remaining DBUS-era management commands to keep landing as gRPC APIs at this cadence. The open question these entries do not answer is whether DBUS is eventually removed or kept indefinitely alongside.
Alternatives to Dragonfly and nfs-ganesha
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Dragonfly or nfs-ganesha.
Casdoor
An identity platform tightening server-side enforcement one micro-release at a time.
skytrackr
Light-based animal geolocation gets a second model that stops assuming the bird sat still.
whirl
whirl turned script logging into a standardized provenance artifact regulators can read.
ESPHome
ESPHome ships on a calendar, and the August beta train is now four builds deep.
rapr
rapr generalises its Rangeland Analysis Platform API access one endpoint at a time
See all Dragonfly alternatives → · See all nfs-ganesha alternatives →
Recent activity from Dragonfly and nfs-ganesha
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 8h agonfs-ganeshaShowExports gains a protocol summary; gRPC FakeRecall API added
- 8h agonfs-ganeshaMemory accounting and CacheMgr gRPC APIs
- 3d agoDragonflyTiering pending-bytes limit unified and exported to metrics
- 5d agoDragonflyBackported memory-accounting fix; FLUSHSLOTS journaled in-transaction
- 12d agonfs-ganeshaMore gRPC commands and RDMA rpcbind registration
- 14d agonfs-ganeshaXCOPY server-side copy and clustered quality of service ⚡
- 18d agoDragonflyi1.39.11: chore(hll): sync hyperloglog.c with valkey upstream (#7961)
- 23d agonfs-ganeshagRPC expands with more stats collection
- 24d agoDragonflyFix mutable cross-thread access on shared reply builder
- 26d agoDragonflyi1.39.9: fix(facade): preserve pub/sub order on unsubscribe (v1 IO loop) (#7909)
- 29d agonfs-ganeshagRPC stats collection ported over from DBUS
- 1mo agoDragonflyi1.39.6: test: skip V2-only pause tests under V1 (#7822)
Frequently asked questions
What is the difference between Dragonfly and nfs-ganesha?
They serve adjacent needs but don't currently overlap on shipped themes. nfs-ganesha is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Dragonfly better than nfs-ganesha?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. nfs-ganesha is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to Dragonfly?
Top Dragonfly alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Dragonfly alternatives" section above for the current picks, or visit /alternatives/dragonfly for the full list with editorial commentary on each.
What are the best alternatives to nfs-ganesha?
Top nfs-ganesha alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "nfs-ganesha alternatives" section above for the current picks, or visit /alternatives/nfs-ganesha for the full list with editorial commentary on each.