What Is Stream Processing?
6 entriesStream processing computes over events as they arrive instead of waiting for batches: filtering, enriching, joining and aggregating unbounded streams with state and time windows. Engines such as Apache Flink and Kafka Streams do this continuously, while streaming databases keep SQL views updated incrementally. Descriptions below follow each project's or vendor's own pages and are not rankings; release facts come from GitHub.
Stream Processing Engines and Frameworks
6 entriesDistributed engines and libraries for stateful stream computation.
SQL Stream Processing and Streaming Databases
5 entriesSystems that express stream processing as continuously updated SQL.
Python, Rust and Developer-First Frameworks
4 entriesLighter-weight libraries and engines for application developers.
Streaming Pipelines, CDC and Storage
5 entriesConnectors, change data capture and streaming storage used with stream processors.
Managed Stream Processing Services
5 entriesCloud and vendor services that run the engines for you.
Reference Reading
6 entriesFoundational articles on streaming systems.
Frequently Asked Questions
What is stream processing?
Computing over events as they arrive rather than in batches, using operations such as filtering, joins, aggregations and windows with managed state. It supports real-time analytics, fraud detection, monitoring and event-driven applications.
What is the difference between Flink, Kafka Streams and Spark Structured Streaming?
Flink is a dedicated distributed engine with strong state and event-time handling. Kafka Streams is a library embedded in your application that reads and writes Kafka topics. Spark Structured Streaming applies Spark's batch APIs to streams and suits teams already on Spark. The best choice depends on your sources, state needs and team skills.
What is a streaming database?
A database such as Materialize or RisingWave that keeps SQL views incrementally up to date as data arrives, so queries return fresh results without rerunning batch jobs. See the Streaming Databases page.
What is event time versus processing time?
Event time is when an event happened, while processing time is when the system handles it. Engines such as Flink and Beam use watermarks to handle late and out-of-order events correctly. The Streaming 101 article explains the concepts.
Should I run stream processing myself or use a managed service?
Managed options such as Amazon Managed Service for Apache Flink, Google Dataflow, Azure Stream Analytics and Confluent Cloud for Apache Flink remove cluster operations, while self-managing Flink or Spark gives control over versions and costs.
How current is this page?
Links and release facts were checked on 31 October 2026 from GitHub and project sites. The O'Reilly and ACM pages returned 403 to automated checks, and the Bytewax site did not respond. Vendor descriptions follow their own pages and are not rankings.