– – Deploy the brand new model to all situations concurrently. All situations in your surroundings are out of service for a short while whereas the deployment happens.
– Rolling – Deploy the brand new model in batches. Every batch is taken out of service through the deployment section, lowering your surroundings’s capability by the variety of situations in a batch.
– Rolling with extra batch – Deploy the brand new model in batches, however first launch a brand new batch of situations to make sure full capability through the deployment course of.
– Immutable – Deploy the brand new model to a contemporary group of situations by performing an immutable replace.
– Blue/Inexperienced – Deploy the brand new model to a separate surroundings, after which swap CNAMEs of the 2 environments to redirect site visitors to the brand new model immediately.
| Technique | Influence of Failed Deployment | Deploy Time | Zero Downtime | No DNS Change | Rollback Course of | Code Deployed To |
|---|---|---|---|---|---|---|
| Downtime | 1 | No | Sure | Handbook Redeploy | Present Cases | |
| Rolling | Single batch out of service; any profitable batches earlier than failure working new software model | 2.5 | Sure | Sure | Handbook Redeploy | Present Cases |
| Rolling with extra batch | Minimal if first batch fails; in any other case, much like Rolling | 3.5 | Sure | Sure | Handbook Redeploy | New and Present Cases |
| Immutable | Minimal | 4 | Sure | Sure | Terminate New Cases | New Cases |
| Blue/inexperienced | Minimal | 4 | Sure | No | Swap URL | New Cases |
