nuggets
nuggets keeps compounding on the 2.0 rewrite — more pattern families, lighter install.
A side-by-side editorial comparison of Dokku and RabbitMQ — release velocity, themes, recent moves, and the top alternatives to consider.
Dokku is quietly turning into a k3s front-end with a JSON-first CLI.
The 0.38 patch line keeps shipping small releases with real features in them. v0.38.27 drops the local-image requirement for k3s deploys, reports Traefik DNS-provider variables as global keys, adds storage directory mode and removal flags, and introduces a vector-cron-sink so scheduled cron output has somewhere to go. It follows v0.38.26, which brought wildcard domains, custom cert issuers, and kernel sysctls to the k3s scheduler.
Two parallel trains, and the 'maintenance' label is now hiding real feature work
RabbitMQ is maintaining 4.2.x and 4.3.x side by side, cutting matching patches into both on the same day, and both trains raised their floor to Erlang/OTP 27. Most of the window is correctness work in the Raft-backed subsystems — quorum queues losing metrics after a restart, leaders committing log entries too optimistically, classic queue index paths accumulating slashes, topic bindings with empty routing keys matching everything. The newest 4.3.5, however, is labelled a maintenance release while carrying encrypted management-UI login tokens, a new authentication logging category, ETag support on the definitions endpoint, and a self-deleting Shovel TTL.
The 0.38 patch line keeps shipping small releases with real features in them. v0.38.27 drops the local-image requirement for k3s deploys, reports Traefik DNS-provider variables as global keys, adds storage directory mode and removal flags, and introduces a vector-cron-sink so scheduled cron output has somewhere to go. It follows v0.38.26, which brought wildcard domains, custom cert issuers, and kernel sysctls to the k3s scheduler.
Two threads run through almost every release: closing the gap between the k3s scheduler and the classic single-host path, and making every command machine-readable. The k3s work has moved from basic scheduling to the operational details — certificates, DNS, sysctls, and now deploys that no longer assume a local Docker image — which is the sequence a project follows when it expects the Kubernetes path to become the default rather than the alternative.
Expect the remaining k3s parity gaps to keep closing one release at a time, and expect the logging work started with vector-cron-sink to extend to other task types that currently have no sink.
RabbitMQ is maintaining 4.2.x and 4.3.x side by side, cutting matching patches into both on the same day, and both trains raised their floor to Erlang/OTP 27. Most of the window is correctness work in the Raft-backed subsystems — quorum queues losing metrics after a restart, leaders committing log entries too optimistically, classic queue index paths accumulating slashes, topic bindings with empty routing keys matching everything. The newest 4.3.5, however, is labelled a maintenance release while carrying encrypted management-UI login tokens, a new authentication logging category, ETag support on the definitions endpoint, and a self-deleting Shovel TTL.
The bug pattern remains the tell: nearly every fix is in quorum queues, Khepri or Raft, which is where RabbitMQ moved its metadata and durability story after 4.3.0 removed Mnesia and partition-handling strategies outright. Layered on top is a steady tightening of the operational perimeter — protocol parsers rejecting malformed input strictly across AMQP 1.0, MQTT 5.0 and STOMP, pre-authentication frame limits on stream connections, HTTP API endpoints validating node membership, and headers that stop disclosing supported methods. Feature work is arriving inside patch releases rather than waiting for a minor.
Expect the 4.2.x train to slow toward end-of-life while 4.3.x patches keep absorbing both Khepri edge cases and security-surface work. The encrypted login token, currently opt-in behind a shared cluster secret, is the kind of setting that gets promoted to a default once rolling-upgrade friction is behind it.
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 Dokku or RabbitMQ.
nuggets keeps compounding on the 2.0 rewrite — more pattern families, lighter install.
projoint spent a year on CRAN paperwork, then shipped a correctness fix it flagged itself.
eratosthenes spends 0.1.0 hardening inputs rather than adding chronology methods.
dqcheckr adds drift analysis, then removes the YAML a user had to hand-write.
An actuarial mainstay spends its releases on CI plumbing, not on new mathematics.
EDAForge is a data-quality auditor renamed mid-flight, still finding its CRAN footing.
See all Dokku alternatives → · See all RabbitMQ alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Dokku and RabbitMQ are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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. Dokku and RabbitMQ are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top Dokku alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Dokku alternatives" section above for the current picks, or visit /alternatives/dokku for the full list with editorial commentary on each.
Top RabbitMQ alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "RabbitMQ alternatives" section above for the current picks, or visit /alternatives/rabbitmq for the full list with editorial commentary on each.