NanoMQ
A protocol-layer correctness pass, delivered largely by first-time contributors
A side-by-side editorial comparison of Fellow and Apache RocketMQ — release velocity, themes, recent moves, and the top alternatives to consider.
Fellow's public changelog has been silent since 2021 — no recent direction is observable here.
The visible signal stops in spring 2021. The last few releases were calendar-extension touch-ups: action items appearing directly in the Google Calendar extension, public view-only meeting links for external attendees, and multi-calendar sync within a single Google or Office account. Nothing in this dataset reflects the past several years of Fellow's actual work.
The RocksDB migration reaches native code as the legacy DLedger broker mode is marked for removal
The 5.x line continues to replace storage internals with RocksDB and to retire the mechanisms it supersedes. 5.5.1, the first release since April, swaps the pure-Java ConsumeQueue compaction filter for a native RocksDB CqCompactionFilter behind a cross-platform JNI shim, drops the shaded rocketmq-rocksdb dependency, and deprecates the legacy Broker DLedger mode. Lite Mode, introduced in 5.5.0, received stability work rather than the client-side adoption path it still needs. Alongside this sit fastjson 1.x removal and a long list of Proxy, Pop and Remoting fixes.
The visible signal stops in spring 2021. The last few releases were calendar-extension touch-ups: action items appearing directly in the Google Calendar extension, public view-only meeting links for external attendees, and multi-calendar sync within a single Google or Office account. Nothing in this dataset reflects the past several years of Fellow's actual work.
From the entries alone, no current trajectory can be inferred — the data is years stale. Whether Fellow has shifted to AI-meeting-notes or remained focused on the original meeting-management surface is not visible here and would be guesswork to assert.
Predictions can't be grounded in this data. The most useful next step is to refresh Fellow's changelog source so that present-day moves are captured.
The 5.x line continues to replace storage internals with RocksDB and to retire the mechanisms it supersedes. 5.5.1, the first release since April, swaps the pure-Java ConsumeQueue compaction filter for a native RocksDB CqCompactionFilter behind a cross-platform JNI shim, drops the shaded rocketmq-rocksdb dependency, and deprecates the legacy Broker DLedger mode. Lite Mode, introduced in 5.5.0, received stability work rather than the client-side adoption path it still needs. Alongside this sit fastjson 1.x removal and a long list of Proxy, Pop and Remoting fixes.
The storage convergence is now deep enough to cross the JNI boundary — RocksDB is no longer an alternate index but the substrate, and the project is willing to take on native build complexity across platforms to get its performance. In parallel, deprecating legacy Broker DLedger narrows the replication story toward the jRaft controller, cutting a maintenance branch rather than carrying both. Lite Mode remains the open bet: it is being maintained but not yet extended outward to clients.
With legacy DLedger deprecated rather than removed, a following release that deletes it outright is the natural next step. Whether Lite Mode gains the client and proxy support it needs is still unresolved — 5.5.1 fixed it without broadening it.
Other Comms 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 Fellow or Apache RocketMQ.
A protocol-layer correctness pass, delivered largely by first-time contributors
Cliq 7.0 stops being a destination app and becomes a layer across Zoho
Netcore's feed remains a demand-generation channel; ten entries, zero product releases.
Element Web is opening an extension surface while rebuilding its timeline underneath.
Signal's beta train keeps trickling small comfort settings between maintenance drops
respond.io is widening what a conversation can hold - more channels, and now more than one owner.
See all Fellow alternatives → · See all Apache RocketMQ alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Apache RocketMQ is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Apache RocketMQ is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Comms products to evaluate alongside.
Top Fellow alternatives in Comms are ranked by recent ship velocity. Browse the "Fellow alternatives" section above for the current picks, or visit /alternatives/fellow for the full list with editorial commentary on each.
Top Apache RocketMQ alternatives in Comms are ranked by recent ship velocity. Browse the "Apache RocketMQ alternatives" section above for the current picks, or visit /alternatives/rocketmq for the full list with editorial commentary on each.