From the course: Site Reliability Engineering Essential Training
Join today to access over 25,300 courses taught by industry experts.
Rolling back changes
From the course: Site Reliability Engineering Essential Training
Rolling back changes
In this final section of this lesson, let's look at rolling back changes. This is an important attribute of effective release management. So why roll back? When do you need to roll back? There are several reasons for rolling back. First is failed canary or progressive rollout. In fact, this is one of the good things about doing canary or progressive rollout, you can identify issues early and when you do, you are going to initiate a rollback. Outage or degraded performance. This is unfortunate situation. Let's say your canary and progressive rollouts did not catch the issue, you end up with an outage or a degraded performance after you apply the change. This is another candidate for rolling back changes. Unexpected user impact and this can be localized or this can be global. But in any case, if the user impact is significant enough to warrant a rollback, you will do a rollback. Finally, regression bugs. Even though user impact may not be there, you might actually uncover some bugs…
Download courses and learn on the go
Watch courses on your mobile device without an internet connection. Download courses using your iOS or Android LinkedIn Learning app.