From the course: Continuous Deployment Strategies by Pearson
Unlock this course with a free trial
Join today to access over 25,200 courses taught by industry experts.
Strategy overview
From the course: Continuous Deployment Strategies by Pearson
Strategy overview
Let's take a look at the rolling deployment strategy and try to understand what it is and how it works. A rolling deployment is done when multiple instances are behind a load balancer and are gradually swapped out with a new version, one node or section at a time, while that load balancer is ensuring traffic arrives safely during that transition. Node by node, slowly over time, new instances are added to the mix and old instances are decommissioned. This slowness is on purpose. We want it to be slow to give us the chance to test out each node and get some feedback on how we're doing before we continue on to the next node. With each new node coming online, we perform a health check or a smoke test to make sure nothing obvious is out of sorts. If all is well, we decommission the old node and continue with the rollout. If we find a problem, we signal a rollback. During the process, the load balancer continues to direct traffic to available nodes, both new and old. Of course, this…