Repo brief: nathanmarz/storm

Generated by RepoPilot · document generated 2026-09-14 · concise human review Evidence snapshot · analyzed 2026-09-14T23:54:12.456Z · commit cdb116e94266

Verdict

Mixed — Stale — last commit 9y ago

• 14 active contributors
• Distributed ownership (top contributor 39% of recent commits)
• Apache-2.0 licensed
• Tests present

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests

What it is

Apache Storm is a distributed stream processing engine for real-time computation of unbounded data streams. It provides fault-tolerant, scalable processing via topologies (DAGs of spouts and bolts), built-in distributed RPC, and state management through its Acker daemon that guarantees at-least-once tuple processing semantics. Monorepo structure: storm-core/ contains the main engine with src/clj/backtype/storm/daemon/ holding critical daemons (nimbus.clj for cluster manager, supervisor.clj for node manager, executor.clj for task execution, acker.clj for reliability). Commands live in src/clj/backtype/storm/command/. Configuration defaults in conf/defaults.yaml, logging via…

Start here

Open these first:

• storm-core/src/clj/backtype/storm/daemon/nimbus.clj — Nimbus daemon—the master scheduler and coordinator for all Storm topologies; understanding job submission, scheduling, and…
• storm-core/src/clj/backtype/storm/daemon/supervisor.clj — Supervisor daemon that manages worker processes on individual nodes; critical for understanding task assignment and…
• storm-core/src/clj/backtype/storm/daemon/worker.clj — Worker process implementation handling tuple routing, messaging, and task lifecycle; the runtime engine for executing bolts…
• storm-core/src/jvm/backtype/storm/Config.java — Central configuration constants and validation; all topology config keys and cluster settings are defined here
• storm-core/src/clj/backtype/storm/daemon/executor.clj — Executor abstraction for running bolt/spout task instances; handles parallelism, threading, and tuple emission/acknowledgment

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

Clone the Apache fork (not this one): git clone https://github.com/apache/incubator-storm.git && cd incubator-storm. For this historical repo: `git clone https://github.com/nathanmarz/storm.git && cd storm && lein ins…

Daily commands:

Start cluster: ./bin/storm dev-zookeeper (embedded ZK in dev), then ./bin/storm nimbus, ./bin/storm supervisor, ./bin/storm ui (web dashboard on localhost:8080). Submit topology: `./bin/storm jar topology.jar co…

…shortened for this brief.

Key cautions & unknowns

• Stale — last commit 9y ago
• ZooKeeper must be running before Nimbus/Supervisors start (dev-zookeeper helper provided, but production needs external ZK). ZMQ library requires C/C++ build toolchain (see bin/install_zmq.sh—fails silently on some…
• Published-advisory coverage was unavailable for the captured dependencies.
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.