This page introduces you to the Vamp releases concept
First we will clarify the difference between releasing software and deploying software.
There is significant confusion between the terms deploy and release. These two terms refer to different acts, one technical and one business-driven. They should not be used interchangeably.
The key distinction between a deployment and a release is the business purpose.
A deploy or deployment includes all the technical activities needed to make a software system or feature available for use. For example, a fresh Docker container running in a pod on a Kubernetes cluster. The software has passed all checks and tests in your CI/CD pipeline and is ready to receive traffic from production users, but it is not yet receiving any traffic. This part of the process just ensures the new version is healthy and running smoothly. It takes care of all the technical checks and balances, without incurring any of the risk involved in serving actual production traffic. Based on this definition, deploying software is a risk-free activity. A release comes after a deployment and includes all the activities needed to move part, or all, of production traffic to the new version. All the business risks and problems (such as downtime, lost revenue, and unhappy customers) are related to the release, not to the deployment. Releasing software is riskier than deploying software. You may choose to release a new version as soon as it is deployed into production, but that should be a conscious business decision. When done correctly, deploying a new version of a microservice to production should have no direct impact on your users' experience. You want your users to enjoy the new features and improvements, thereby getting greater value from your product. However, there is always a risk the new version will deliver a degraded user experience. This could be the result of technical issues, or perhaps because your users do not like the product features and improvements in that new version. Vamp's Continuous Release Orchestration solution provides you with the tools to manage that risk. Vamp simultaneously protects your users' experience and ensures new microservices versions are truly delivering additional business value.
Copy link