liveBook · Manning

Event replay

As explained in The Coder Cafe

Past-event replay executes recorded historical inputs against a system version to evaluate resulting behavior.

Event replay runs recorded historical inputs against a new system version, then analyzes the resulting behavior before deployment. It turns proposed changes into controlled experiments rather than predictions alone. section 6.14.2

A practical replay workflow:

Replay differs from deterministic simulation testing: replay uses real historical inputs, while deterministic simulation creates controlled, repeatable conditions. Both approaches depend heavily on observability. section 6.14.2

How The Coder Cafe covers it

How deep it goes
Defines recording, replay, and impact analysis, but does not detail event formats or implementation mechanics.
Examples
Uses recorded system inputs replayed against a new version and compares the resulting impact.
What it assumes
Assumes systems record inputs and provide observability for analyzing replayed behavior.
What you can do after
Evaluate proposed changes in a controlled setting before deploying them to real users or conditions.
How it connects
Connects event replay with simulation testing, deterministic simulation testing, observability, and decision-making under uncertainty.

Also explained in

Compare how 2 books explain event replay →

Related concepts

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