On May 15th, I participated in a lecture on continuous delivery, agile, and DevOps in practice, some of which were very inspiring. Several viewpoints (ideas, principles) have been sorted out for sharing.
- Continuity of development in agile iterations, should not be demarcated (beginning or ending) with distinct iterations: http://lzhted.iteye.com/blog/2211955
- Automated testing strategy and delivery pipeline: http://lzhted.iteye.com/blog/2212646
- Deployment mode
This article introduces the third point, three deployment modes:
- Blue-green deployment model
- PHOENIX Deployment Mode
- Canary Deployment Mode
The blue-green deployment mode can be easily understood as shown in the figure below. The deployment of the production link is divided into two sets of environments (respectively become the blue environment and the green environment, and the data is interoperable). The environment that users actually access is controlled by routing. The versions of the blue and green environments are the same, or one of them is the actual production system. , the other is the latest version environment to be launched (UAT, Beta). When the latest version passes the acceptance and decides to release, you can switch the version directly by simply adjusting the routing.
The advantages include: 1. Fast launch, very little or no user perception; 2. Conducive to piloting new functions in the production link in advance; 3. Conducive to fault control, any set of environment failures can be carried out very conveniently Version rollback and environment switching.
The PHOENIX deployment mode is shown in the figure below. The difference from the blue-green mode is that after the version is switched, the original environment resources are released, which is conducive to the recycling of resources. Just like a phoenix, a bird (a system) becomes a more beautiful phoenix (a new system) after being reborn from ashes. 
The Canary deployment mode, as shown in the following figure, accesses multiple services through routing, and these services provide the functions required by the system within the specified scope. These services are generally of the same version, but can also be deployed as different versions if needed for A/B testing, performance testing, etc. The biggest advantage of the Canary mode is that it makes testing in the production environment a reality (some products must be verified in the production process). When the verification passes, all services can be deployed. If the verification fails, the version can be rolled back. See: http://www.infoq.com/news/2013/03/canary-release-improve-quality
