liveBook · Manning

Streaming table

A streaming table is a continuously updated relation that retains the latest value associated with each key in a data stream.

How 2 Manning books explain it

Apache Kafka in Action

A stream processing table is a continuously updated key-value representation of current state derived from records in a stream.

How it is used
Provides queryable current state alongside real-time stream processing, avoiding external database queries for state held in the application.
How deep it goes
Explains key-value structure, topic replay, partitioning, local state, changelog recovery, aggregations, and joins.
Examples
Uses product state, account transaction totals, count aggregations, topic compaction, and stream-table joins as concrete examples.
What you can do after
Apply it via Kafka Streams or Flink to derive, query, aggregate, join, and recover current state from topics.

Read how Apache Kafka in Action explains streaming table →

Kafka for Architects

A stream-processing table is a view that retains the latest value associated with each key rather than treating every update as an independent event.

How it is used
Supports stream-table joins by retaining the latest customer value for lookups triggered by incoming orders.
How deep it goes
Explains latest-value semantics, lookup triggers, non-reprocessing, copartitioning, and GlobalKTable, while deferring advanced join types.
Examples
Uses customer data joined with orders, contrasted with payment and order stream-to-stream joins.
What you can do after
Apply it via Kafka Streams to look up customer data for incoming orders with aligned keys and partitions.

Read how Kafka for Architects explains streaming table →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.