Reading / Event streams

A sequence of things that happened

An event records that something happened. A stream lets programs work with a continuing sequence of those records.

Separate the record from the reaction

In an event-driven system, a producer creates events and consumers respond to them through a channel. With event streaming, records can be retained so that readers track their own position and revisit earlier events. Different consumers can use the same sequence for different purposes.

The event and its interpretation remain distinct. A record might say that an item moved, while a consumer updates a display or calculates a summary. Those reactions do not have to happen at precisely the same moment.

Hypothetical example · A shared drawing

Imagine a drawing tool recording that a shape was added, moved, then removed. One reader could update a view of the drawing; another could build a history panel. If a reader pauses, it might later catch up from its previous position. The example assumes records are retained and readable in the needed order. It does not describe a MASSAGUET LLC application.

Event recordsDrawing viewHistory view

Ask what the sequence guarantees

The surrounding system determines how long events remain available, how ordering works, and what happens when processing is repeated. Readers may temporarily disagree because they have reached different positions. A useful explanation therefore names the guarantees instead of assuming every event arrives once, everywhere, in one universal order. Start with the record, then examine each reader’s responsibilities.

Further reading: Microsoft’s event-driven architecture guide.