liveBook · Manning

Data stream

As explained in Grokking Software Architecture

An event stream is an ordered sequence of events representing changes, observations, or occurrences over time.

A data stream is an ordered sequence of events over time. Streams can record system signals for reconstructing what happened, or carry ongoing database changes during a migration. section 7.6.3 section 12.5.2

When moving data to a new service, pair the stream with a snapshot:

  • Copy historical records in a one-time snapshot, then stream new changes until the systems are synchronized. Streaming alone does not replace the initial copy. section 12.5.2
  • Use logged events to correlate signals and distinguish related symptoms from separate problems. section 7.6.3

One failure, two signals

A falling oxygen-tank pressure and a matching fuel-cell power loss point to one underlying problem. Correlating the event streams helps reconstruct what is happening. section 7.6.3

How Grokking Software Architecture covers it

How deep it goes
Explains logged events and real-time database deltas, but does not detail ordering guarantees or delivery mechanics.
Examples
Uses correlated oxygen-pressure and fuel-cell signals, plus a snapshot followed by streamed billing-data changes.
What you can do after
Understand how event streams reveal related system failures and keep migrated data synchronized.
How it connects
Connects streams to event-driven architecture, database migration, and change data capture.

Also explained in

Compare how 6 books explain data stream →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Software Architecture. The section links point to the parts of the book it draws on.