4 ms·
Interesting! So you'd provision a new VM, deploy and add it to the LB, and then destroy the old node? I think that's where a docker-based deployment would shine
by memset 3y ago
Interesting! So you'd provision a new VM, deploy and add it to the LB, and then destroy the old node? I think that's where a docker-based deployment would shine, it would be way faster.
- bluehatbrit 3y agoThis is how I've done things in the past when working with VM's. It definitely works well with containers as well though. The really great benefit is you can check the new version is healthy before introducing it to public traffic, and then you can hold off as long as you want before pushing on with replacing the other nodes. You also make sure you get a clean VM each time configured the way your IaC dictates. Obviously if your nodes hosting the application are not under IaC or for some reason you want them to be long lived, then this doesn't work as well and your model is going to the better way to go.