Skip to content

Recreate Deployment

Recreate Deployment (also known as Re-create) is a deployment strategy where the old version of an application is completely shut down before the new version is brought online.^[400-devops-06-kubernetes-k8s-ithelp-day12-readme.md]

This approach is characterized by a defined period of downtime, during which the service is unavailable to users.^[400-devops-06-kubernetes-k8s-ithelp-day12-readme.md] The duration of this service interruption is dependent on the time required to terminate the old application and start the new one.^[400-devops-06-kubernetes-k8s-ithelp-day12-readme.md]

Characteristics

  • Simplicity: It is considered easy to set up and configure.^[400-devops-06-kubernetes-k8s-ithelp-day12-readme.md]
  • Single Version: Only one version of the application runs at a time during the deployment process.^[400-devops-06-kubernetes-k8s-ithelp-day12-readme.md]
  • Resource Efficiency: It does not place extra load on the host infrastructure, as it does not run two versions simultaneously.^[400-devops-06-kubernetes-k8s-ithelp-day12-readme.md]

Disadvantages

The primary drawback of this strategy is the significant impact on users due to the required downtime.^[400-devops-06-kubernetes-k8s-ithelp-day12-readme.md] Additionally, the cost of the downtime is directly related to how long it takes to shut down the old service and boot the new one.^[400-devops-06-kubernetes-k8s-ithelp-day12-readme.md]

Sources

  • 400-devops-06-kubernetes-k8s-ithelp-day12-readme.md