问题描述
蓝/绿部署和滚动部署有什么区别?我一直认为蓝/绿部署是从旧版本到新版本的流量突然切换.
What's the difference between a blue/green deployment and a rolling deployment? I always thought that a blue/green deployment was a sudden switch of traffic from the old version to the new version immediately.
这个关于 AWS 上的蓝/绿部署的讨论展示了实施蓝/绿部署，但它们似乎也符合滚动部署的定义.
This talk about Blue/Green deployment on AWS shows various different strategies to implement a blue/green deployment, but they also seem to match the definition of a rolling deployment.
蓝/绿部署是滚动部署的子集吗?
Is a blue/green deployment a subset of rolling deployments?
推荐答案
我在这里写了一篇关于这个主题的文章:http://blog.itaysk.com/2017/11/20/deployment-strategies-defined
I have written an essay on this topic here: http://blog.itaysk.com/2017/11/20/deployment-strategies-defined
在我看来，不同之处在于是通过替换现有设置中的实例来应用新版本(在滚动升级的情况下)，还是为新版本创建一个完全隔离的设置(在蓝/绿的情况下)).在我看来，蓝/绿是最安全的策略，并且在大多数情况下对于生产部署来说更好.阅读帖子以进行详细比较.
In my opinion the difference is whether the new version is applied by replacing instances in the existing setup (in the case of rolling upgrade), or a completely isolated setup is created for the new version (in the case of Blue/Green). In my opinion Blue/Green is the safest strategy and is better in most cases for production deployments. Read the post for a detailed comparison.
这篇关于蓝绿部署与滚动部署?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！