NEW
Also known as: Storm
A real-time computation system for processing data streams.
DESCRIPTION
Apache Storm is a distributed system for real-time computation that processes streams using spouts and bolts assembled into topologies. It provides horizontal scalability, fault tolerance, and low-latency processing. Storm popularized stream processing in early big data ecosystems and integrates with Kafka and other sources. While still usable, many teams have moved to Apache Flink or Spark Structured Streaming for richer APIs and state management. Storm remains relevant where lightweight, topology-based stream computation fits legacy environments.
ALTERNATIVE DEFINITIONS
Apache Storm
Apache Storm is a free and open source distributed realtime computation system.
Emphasizes distributed and real-time computation with open-source licensing.
Wikipedia
Apache Storm is a distributed stream processing computation framework written predominantly in the Clojure programming language.
Notes stream processing focus and primary language.
RELATED TERMS
Stream Processing Spout Bolt Topology Apache Kafka Spark Structured Streaming Trident API Stateful Processing Backpressure
COMPETING TERMS
Apache Flink Apache Spark Structured Streaming Apache Samza
RELATIONS
- Broader: Stream Processing
KNOWLEDGE AREAS
Real-time & Streaming Data Data Engineering Platform & Tooling
TARGET AUDIENCE
Data Engineer Software Developer DevOps Engineer
EXTERNAL SOURCES
- Wikipedia - Apache Storm
- Apache Storm - Core concepts: spouts, bolts, topologies
- Apache Flink - Modern stream processing alternative
TOP QUESTIONS
What is Apache Storm used for?
Storm processes unbounded data streams in real time using topologies of spouts and bolts, enabling event-driven analytics and transformations.
Category: Definition
Is Apache Storm still relevant?
It remains usable, but many teams prefer Flink or Spark Structured Streaming for advanced stateful processing and unified batch/stream APIs.
Category: Opinion
How does Apache Storm scale?
Topologies distribute bolts across workers and nodes; the cluster scales horizontally to handle higher throughput.
Category: HowTo
What are common pitfalls with Storm?
Complex topology management, limited state support compared to newer frameworks, and operational overhead can challenge teams.
Category: Mistakes
What risks arise with outdated Storm deployments?
Maintenance burden, fewer community resources, and limited features compared to modern stream processors may hinder evolution.
Category: Risks
What are alternatives to Apache Storm?
Apache Flink, Spark Structured Streaming, and Apache Samza provide richer APIs and state models.
Category: Alternatives
How does Storm integrate with Kafka?
Spouts consume from Kafka topics, bolts process events, and results are emitted to sinks or other topics.
Category: Related
Where to learn Apache Storm?
Start with official concepts docs, build a simple topology, and benchmark against newer frameworks for fit.
Category: HowTo
What’s a simple analogy for Storm topologies?
Think of an assembly line where spouts feed raw materials and bolts perform sequential transformations.
Category: Example