How release canaries can save your bacon
cloudplatform.googleblog.com
How release canaries can save your bacon
1–10 of 54 posts
Re: How release canaries can save your bacon
#2If you are interested in canary deployments, check out Spinnaker by Netflix: http://www.spinnaker.io/ There's a good talk about it here with stories from Waze and Google: https://www.youtube.com/watch?v=05EZx3MBHSY
Re: How release canaries can save your bacon
#3As a high traffic customer of Google, I've been this person far too many times.
[...] if it breaks, real users get affected, so canarying should be the first step in your deployment process, as opposed to the last step in testing.
Re: How release canaries can save your bacon
#4As a high traffic customer of Google, I've been this person far too many times. [...] if it breaks, real users get affected, so canarying should be the first step in your deployment process, as opposed to the last step in testing. It's a fine pattern and all, but not an excuse to throw stuff at prod and see what happens.
What's a high traffic customer of Google?
Re: How release canaries can save your bacon
#5As a high traffic customer of Google, I've been this person far too many times. [...] if it breaks, real users get affected, so canarying should be the first step in your deployment process, as opposed to the last step in testing. It's a fine pattern and all, but not an excuse to throw stuff at prod and see what happens.
What's a high traffic customer of Google?
I assume they mean they visit the site frequently
Re: How release canaries can save your bacon
#6As a high traffic customer of Google, I've been this person far too many times. [...] if it breaks, real users get affected, so canarying should be the first step in your deployment process, as opposed to the last step in testing. It's a fine pattern and all, but not an excuse to throw stuff at prod and see what happens.
I think the author of that sentence agrees with you. It's saying you should think of a canary as something to do only after testing is complete, not as a means of testing.
Re: How release canaries can save your bacon
#7As a high traffic customer of Google, I've been this person far too many times. [...] if it breaks, real users get affected, so canarying should be the first step in your deployment process, as opposed to the last step in testing. It's a fine pattern and all, but not an excuse to throw stuff at prod and see what happens.
>but not an excuse to throw stuff at prod and see what happens
The problem with production traffic is you will never be able to simulate it perfectly. At the end of the day you are required to flip a switch and test things out in the wild.
Re: How release canaries can save your bacon
#8As a high traffic customer of Google, I've been this person far too many times. [...] if it breaks, real users get affected, so canarying should be the first step in your deployment process, as opposed to the last step in testing. It's a fine pattern and all, but not an excuse to throw stuff at prod and see what happens.
What's a high traffic customer of Google?
Presumably someone who sells or buys lots of ads?
Re: How release canaries can save your bacon
#9Yes, a Canary lets you limit the damage if some bug sneaks past testing. We've done it for over 10 years, with staged rollouts and automated crash statistics and such.
The draw back is that prod needs to be tolerant of multiple versions. Which is usually a fine practice in itself, anyway!
Re: How release canaries can save your bacon
#10Interesting. I've heard of this practice as 'one box' or 'one pod'. And canary used to mean, 'tests that run continously against your production stack.'
I wonder which is more prevalent.