liveBook · Manning

Deployment validation

As explained in Grokking Software Architecture

A release check that confirms a deployment reached its intended targets and that they are running the matching build.

A fleet can look deployed while one machine quietly runs yesterday’s code. Deployment validation checks each target for the intended build and catches mismatches before the rollout proceeds. section 13.9.3

Seven updated, one forgotten

In Knight Capital’s eight-server deployment, seven servers received the new files and one remained on the old binary. A check for the matching build across all targets could have caught the mismatch before production opened. section 13.9.1 section 13.9.3

Figure 13.13 The Knight Capital Failure: Because no automated deployment verification checked that all eight servers were synchronized, one mismatched node acted like an automated firehose for unauthorized trades.

See how one out-of-sync server can undermine an otherwise completed deployment. section 13.9.1

How Grokking Software Architecture covers it

How deep it goes
Checks all nodes against a matching build tag and can halt rollout on a mismatch, without detailing the check’s implementation.
Examples
Uses Knight Capital’s eight-server rollout, where seven servers received new files and one remained on the old binary.
What you can do after
Apply via an automated deployment pipeline to verify each target’s build tag and block a mismatched rollout.
How it connects
Connects deployment validation with CI/CD pipelines, immutable container images, and automated deployment engines.

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.