The stream API
Application Id (application.id): Each stream processing application must have a unique id.
This id is used in the following places to isolate resources used by the application from others:
When an application is updated, it is recommended to change application.id unless it is safe to let the updated application re-use the existing data in internal topics and state stores. One pattern could be to embed version information within application.id, e.g., my-app-v1.0.0 vs. my-app-v1.0.2.
- A stream processor is a node in the processor topology that represents a single processing step.
- A stream is an unbounded, continuously updating data set.
- A low-level Processor API that lets you add and connect processors as well as interact directly with state stores.
|Description / why needed
|Base library for Kafka Streams. Required.
|Kafka client library. Contains built-in serializers/deserializers. Required.
|Apache Avro library. Optional (needed only when using Avro).
|Confluent’s Avro serializer/deserializer. Optional (needed only when using Avro).
Code / Demo
- Code examples that demonstrate how to implement real-time processing applications using Kafka Streams. See readme.