What is Blue-green Deployment, Canary release?
Problem: Traditionally, we deploy a new release by replacing the current one. The old release is stopped, and the new one is brought up in its place. The problem with this approach is the downtime occurring from the moment the old release is stopped until the new one is fully operational Having monolithic applications introduces additional problems like, for example, the need to wait a considerable amount of time until the application is initialized. Solution: variation of the blue-green deployment process . At any time, one of the releases should be running meaning that, during the deployment process, we must deploy a new release in parallel with the old one. The new and the old releases are called blue and green. With the blue-green process, not only that we are removing the deployment downtime, but we are also reducing the risk the deployment might introduce. If we combine the blue-green process with immutable deployments (through VMs in the past and though Docker co
