Resend
Resend is wiring itself into every agent runtime it can reach, and now adding the controls to stop a send.
A side-by-side editorial comparison of RabbitMQ and Skipper — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Zalando's ingress proxy finally speaks HTTP/2 cleartext end to end
Skipper ships patch tags almost daily, and most carry a single dependency bump or a one-line auth fix. The substance in this window is v0.27.57, which enables h2c on the server handler, the proxy client, and the net client, with a new h2c:// route scheme and Kubernetes appProtocol wiring. Everything else in the window is Dependabot traffic and two narrow fixes to token introspection and grant auth.
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.
Skipper ships patch tags almost daily, and most carry a single dependency bump or a one-line auth fix. The substance in this window is v0.27.57, which enables h2c on the server handler, the proxy client, and the net client, with a new h2c:// route scheme and Kubernetes appProtocol wiring. Everything else in the window is Dependabot traffic and two narrow fixes to token introspection and grant auth.
The release cadence is a stream of small, individually unremarkable tags where the occasional protocol or load-balancing change is the only thing worth reading. Recent substance has clustered on the data path: leastRequests balancing in v0.27.53, h2c now. The auth filters are being maintained rather than extended, with fixes rather than new capability.
Expect the h2c work to generate follow-up fixes as it meets real gRPC backends, since the release notes already show HTTP Upgrade negotiation failing while direct prior knowledge works.
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 RabbitMQ or Skipper.
Resend is wiring itself into every agent runtime it can reach, and now adding the controls to stop a send.
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
Casdoor is spending its release cadence moving auth checks from the client to the server
ESPHome ships on a calendar, and the August beta train is now five builds deep
Strimzi's 1.2.0 candidate closes with a logging fix and nothing else
Prowler's assistant decides what to do with findings; the patches keep the scanner honest
See all RabbitMQ alternatives → · See all Skipper alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. RabbitMQ and Skipper 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. RabbitMQ and Skipper 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 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.
Top Skipper alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Skipper alternatives" section above for the current picks, or visit /alternatives/skipper for the full list with editorial commentary on each.