LoginSign Up
← Back to all sparks
A

Apache RocketMQ

COMMS
Velocity0.0

Distributed messaging and streaming platform

rocketmq.apache.org ↗

RocketMQ built a stripped-down subscription mode for AI workloads — then went quiet for four months.

message-brokerrocksdblite-modeai-workloadsaclapache
◆Current state
The 5.x line has spent this window replacing storage internals and tightening the security model. RocksDB moved from an experimental ConsumeQueue index to backing Pop consumption, timer messages, transaction messages and indexes; ACL 1.0 was removed outright in favour of ACL 2.0; priority messages arrived in 5.4.0. The most recent release, 5.5.0 in April, introduced Lite Mode — a lightweight subscription mechanism with its own message processor, long-polling service and protocol support, explicitly framed for AI scenarios. Nothing has shipped since.
◆Where it's heading
Two forces are shaping the project. Underneath, the storage layer is converging on RocksDB across every subsystem that used to have its own file format, which is a multi-release migration with a stated plan rather than an opportunistic change. Above it, Lite Mode is a bid to be the broker for many small, resource-light consumers rather than a few heavyweight ones — the shape AI agent and inference workloads take. The four-month gap since 5.5.0 makes it hard to tell whether that bid is being pressed or parked.
◆Prediction
Lite Mode arrived without client-side adoption guidance, so the obvious next step is client and proxy support to make it usable end-to-end — but with no release since April, the entries do not support a confident read on timing.

◆Recent moves

  1. 3mo ago

    5.5.0 adds Lite Mode, a lightweight subscription path for AI workloads

    ⚡ SPARK

    The clearest statement of intent in this window: a second, lighter subscription mechanism sitting beside the existing one, complete with its own processor, long-polling service and protocol support. It is the first release here aimed at a workload shape rather than at RocketMQ's existing operators.

    View source ↗
  2. 7mo ago

    5.4.0: priority messages and RocksDB-backed timer, transaction and index

    Two substantial RIPs land together — priority messages, and RocksDB as the store behind timer messages, transaction messages and indexes. The second continues the migration begun in 5.2.0, pulling another set of subsystems off their bespoke formats onto a common engine.

    View source ↗
  3. 7mo ago

    5.3.4: TimerWheel snapshots and Netty, OpenTelemetry upgrades

    A stability release whose one durable change is the TimerWheel snapshot mechanism for reliable recovery — the kind of fix that only matters after a broker restarts badly. The rest is dependency currency and scattered Broker, Proxy and Client corrections.

    View source ↗
  4. 1y ago

    5.3.3 drops ACL 1.0 in favour of ACL 2.0

    Removing ACL 1.0 outright is a breaking change dressed as a minor release, and it forces migration onto the ACL 2.0 model introduced in 5.3.0. The project is willing to cut old surface rather than carry two authorisation systems.

    View source ↗
  5. 1y ago

    5.3.2: RocksDB-based Pop consumption enters alpha

    The first appearance of RocksDB behind Pop consumption, shipped in alpha with a stated migration plan — the opening move of the storage convergence that 5.4.0 later extends. Cancellable scheduled messages and graceful online/offline handling round it out.

    View source ↗
  6. 1y ago

    5.3.1: bug fixes and test coverage

    A maintenance release of bug fixes and added test coverage across the admin and client paths, with no user-visible capability change.

    View source ↗