<story><title>How release canaries can save your bacon</title><url>https://cloudplatform.googleblog.com/2017/03/how-release-canaries-can-save-your-bacon-CRE-life-lessons.html</url></story><parent_chain></parent_chain><comment><author>luctor_ad_astra</author><text>A quick rollback frees up the developer&amp;#x27;s contextual burden and makes it easy to take calculated risks. This works better in some environments, of course. You wouldn&amp;#x27;t want it in testing a medical support system, for example. LinkedIn goes a bit further and has continuous release monitoring: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;engineering.linkedin.com&amp;#x2F;blog&amp;#x2F;2015&amp;#x2F;11&amp;#x2F;monitoring-the-pulse-of-linkedin&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;engineering.linkedin.com&amp;#x2F;blog&amp;#x2F;2015&amp;#x2F;11&amp;#x2F;monitoring-the...&lt;/a&gt;</text></comment>
<story><title>How release canaries can save your bacon</title><url>https://cloudplatform.googleblog.com/2017/03/how-release-canaries-can-save-your-bacon-CRE-life-lessons.html</url></story><parent_chain></parent_chain><comment><author>jwatte</author><text>Yes, a Canary lets you limit the damage if some bug sneaks past testing. We&amp;#x27;ve done it for over 10 years, with staged rollouts and automated crash statistics and such.&lt;p&gt;The draw back is that prod needs to be tolerant of multiple versions. Which is usually a fine practice in itself, anyway!</text></comment>