Apache Storm vs Apache Superset

Storm is running two lines: a 2.8.x maintenance branch that is mostly Dependabot traffic punctuated by real security releases, and the new 3.0.0 line cut on 22 July. 3.0.0 removes all remaining Clojure from the codebase, raises the baseline to Java 21 (with master already on 25), and ships throughput work — zstd compression for thrift cluster state, tuple compression between workers, and decoupling of the control plane from the data plane on receive queues. The 2.8.6 and 2.8.7 releases earlier in the window carried four CVEs, including a deserialization RCE reachable by any user with topology submission rights.

The project is converting itself from a legacy JVM codebase into an ordinary modern Java one, and the 3.0 work shows where that energy goes next: scheduling and queueing. Recent PRs add AIMD dynamic batch sizing to JCQueue, jitter metrics and a jitter-aware stream grouping, round-robin rebalance onto returning supervisors, and several fixes for stale or orphaned worker heartbeats. Alongside that, the distribution is being slimmed — optional Hadoop and Kafka dependencies were unbundled and shared jars de-duplicated. The 2.x branch is being kept alive for security and dependency currency, not for features.

Expect 3.0.x point releases to concentrate on the scheduler and worker-lifecycle fixes that 3.0.0 opened up, and expect the 2.8.x line to keep receiving CVE backports while feature work stays on 3.x. The Java 25 baseline already on master suggests the next minor will move the floor again.