In general, the project publishing production environment including the last three: blue-green publishing, canary release, A / B testing. Here is some personal understanding, have questions, please correct me, thank you.
Blue-green release
Two identical production environment, and there is no coupling between the two cases. An external service provider for the green environment and not to a set of blue environment. If there are new features before release to the environment of blue, green does not affect the environment. After repeated tests modified to verify there is no problem, the user will be cut to the blue environment, some time after the switch, if there are problems then cut back to a green environment. If not, the environment has become a new blue green environment, green environment of the original release, for the next deployment of a blue environment.
Canary released
Is often said that the gray release. Suppose you have hundreds or even thousands of servers, you can not re-apply for so many hosts to deploy a so-called blue environment. Canary released at this time is undoubtedly the right choice. We talk about the new version of the service posted on the 10 machines which then observe the verification. After confirming no abnormalities, then the update to the remaining servers. It can be used to modify the weights of the way to make a few servers to be accessed priority.
A / B test
A / B testing is different from the blue-green and canary release issued, the first two methods is a release strategy, the goal is to ensure that the new on-line service is the question of whether there is hidden BUG and so on. The A / B testing is a completely test the effect, which allows multiple versions of the same time offer access services, such as A version of the theme is blue, B version of the theme is red, and then compare different versions of subscribers, the final election the most appropriate version.
Writing is not easy, please indicate the source, thank you ~~