Re:Deploys at Slack
by copecopecope on Wednesday April 08, 2020 @05:14PM
(#22817226)
At some point a new build needs to roll out to production. There's always going to be some risk that something goes wrong, so better to test with 2% of the population initially rather than 100%. By then, the build has already gone through integration tests/dog-fooding, so if something goes wrong in the canary phase, it's generally due to some production environment configuration issue.
[ Parent
| on HN ]
Re:Deploys at Slack
by toomuchtodo on Wednesday April 08, 2020 @05:15PM
(#22817244)
Not disagreeing, simply stating users should be aware and get a say (an option would be fine to opt in to early release access), especially if they’re a paying customer.
Re:Deploys at Slack
by copecopecope on Wednesday April 08, 2020 @05:22PM
(#22817308)
I hear where you're coming from, but from my experience, the canary phase usually lasts less than an hour. And the traffic is usually split randomly, so the same 2% of users aren't at elevated risk for every deployment. I don't know how Slack does it, though.