← Back to Concept Contrast

Concept Contrast Fable

Put one car in first to see versus releasing section by section in proportion

Conclusion first:Canary release sends a small portion of traffic to the new version first, then expands once metrics look normal. Gradual rollout increases the new version's share step by step according to a predefined plan. Both control risk, but the core of canary release is deciding after observation, while the core of gradual rollout is advancing according to plan.

Canary release sends a small portion of traffic to the new version first, then expands once metrics look normal. Gradual rollout increases the new version's share step by step according to a predefined plan. Both control risk, but the core of canary release is deciding after observation, while the core of gradual rollout is advancing according to plan.

Fable

Two bridge keepers on two new bridges: one tests with a single person first, the other releases people in batches by headcount

Two new bridges were built outside the old city, completed on the same day. Old Shen, keeper of the east bridge, let two pole-carriers cross first, while he stood at the bridgehead watching the deck for cracks and listening for strange noises. Old Xu, keeper of the west bridge, held a ratio table: in the first hour, let through ten percent of pedestrians; in the second hour, thirty percent; in the third hour, sixty percent; and open the whole bridge before sunset.

The two pole carriers on the East Bridge were halfway across when the bridge deck shook. Old Shen immediately blew his whistle, called the people back, and had the bridge re-inspected. They found slight settlement in the third pier, and the craftsmen reinforced it overnight. The next day, Old Shen first let three carts pass. Once the bridge was stable, he began letting people cross. On the West Bridge, passage was allowed by proportion. By the third hour, 60% of the foot traffic had been let through, and the bridge deck began to sway. Old Xu saw that the plan said 60%, so he did not stop. As a result, the bridge deck swayed even more, and pedestrians started to run.

In the after-action review, the county magistrate asked Old Xu why he had not called a halt. Old Xu said the plan table had no step for deciding after observation, and proportional execution should not be interrupted. Old Shen said his logic was exactly the opposite—every step was try first, then release; if it fails the test, it is not released, and the observation result is the only pass. The magistrate wrote in the file: one decides by observation, the other advances by plan. They cannot be mixed.

In the end, both bridges were repaired. The magistrate ruled that on acceptance day, the new bridge must use Old Shen's method—apply the smallest load first, watch the key indicators, and don't proceed to the next step until they pass. For daily traffic, Old Xu's method could be used—advance in planned segments, because the bridge had already been verified as safe.

The new bridge-keeping apprentice asked a question: if the canary people got through fine, can we just release everything at once? Old Shen said no—the pressure when there are few people and the resonance when there are many are two different things. The canary only tells you that this version can start being released; it does not mean you can release it all in one go.

Later, a diagram was drawn in the bridge keeper's manual: release one or two cars first—observe—release ten percent—observe—release thirty percent—observe—release sixty percent—release all. Canary is the first step; gradual rollout is the whole path. The first step determines whether you can proceed; the later steps control how fast you proceed.

The last page of the manual had one line: a canary not failing does not mean you can release everything at once, and a canary release at 80% not failing does not mean observation is unnecessary. Both terms are saying the same thing—do not put everyone on the bridge all at once.

Canary release

First expose the new version to a very small number of users or traffic, and observe key metrics. Only after metrics are normal should the scope be gradually expanded. The core action is to observe and then decide, not to proceed according to a fixed plan.

Canary release

Gradually shift traffic to the new version according to a predetermined ratio and schedule. The core is to advance according to plan; each stage may have observation, but the decision logic is plan-driven.

Story Mapping

  • Old Shen first releases to two people and observes: canary release, decide after observation, and if it does not pass, do not release
  • Old Xu advanced by one, three, six: canary release, rolling out in planned stages
  • West Bridge released 60% as planned but the swaying did not stop: plan-driven approaches may ignore real-time signals
  • Use Old Shen's method on acceptance day, Old Xu's method for daily operations: canary is suitable for first validation, gray release for stable rollout
  • Passing the canary does not mean releasing everything at once: safety with two people does not equal safety at full load
  • The canary drawn in the manual is the first step: a canary is the first stage of a gradual rollout, but the decision logic is different

Down to release strategy design

For the first launch or a major change, do a canary release first—send a very small proportion of traffic and observe for at least one complete monitoring cycle; if metrics do not meet the standard, roll back directly. After the canary passes, move to a gradual rollout—release traffic in proportional segments, with rollback trigger conditions for each segment. Do not let the gradual rollout replace the canary's observational validation, and do not release everything at once after the canary passes. The way they work together is: the canary decides whether it can go, and the gradual rollout controls how fast it goes.

京ICP备2026014272号