Back to articles

Tag archive

#deployment

What Checks A Release When There Is No Canary
Oct 11, 2026

What Checks A Release When There Is No Canary

Three pipelines, 67 metric records and nine alert rules stand between a commit and everybody - and zero requests go to a canary. Both ways of checking a release before everyone ask the same thing of a system, and it is not the second binary: a canary needs a mark that survives the whole chain, shadow traffic needs writes separated from reads. Here is what each one demands, and what is holding the line instead.

Oct 11, 202611 min read0 reactions0 comments
T
Oct 10, 2026

The Mark That Stops After The First Hop

Standing a new version beside the old one is the cheap half. The technique only works if the mark on the request survives every hop - and an audit of my own service had already answered that: the publish was going out with empty headers, so nothing that rides in headers crossed the queue. Two generations of code alive at once, a contract compatible in both directions, and a price that is organisational rather than technical.

Oct 10, 202611 min read0 reactions0 comments