问题描述
我正在使用弹性beantalk来处理我的部署.我已阅读了有关这些部署选项的说明，但并不清楚.有人可以用更简单的语言来解释它吗?我正在尝试构建一个nodejs部署系统.
I am using elastic beanstalk to handle my deployments. I read the explanation for these deployment options but it was not quite clear.Could someone explain it in more simpler words please ? I am trying to build a nodejs deployment system.
任何帮助将不胜感激！
谢谢！
推荐答案
我认为这会有所帮助.
不可变–首先将应用程序代码部署到一个新创建的EC2实例中.一旦在第一个实例上成功部署，就创建了创建并行队列所需的剩余实例数，并将应用程序代码部署到了它们.在整个并行机群上成功部署之后，运行旧应用程序版本的实例一次终止25％.此部署策略可确保将失败的部署的影响降到最低(即单个EC2实例)，并使您的应用在正在进行的部署过程中以最大容量提供流量.
Immutable – starts by deploying your application code to a single newly created EC2 instance. Once the deployment succeeds on the first instance, the remaining number of instances required to create a parallel fleet are created and the application code is deployed to them. After the deployment succeeds on the entire parallel fleet, instances running the old application version are terminated 25% at a time. This deployment policy ensures that the impact of a failed deployment is minimal (i.e.: a single EC2 instance) and enables your application to serve traffic at full capacity during an ongoing deployment.
附加批处理滚动–首先将应用程序代码部署到新创建的EC2实例的单个批处理中.一旦在第一批实例上成功部署，应用程序代码就会分批部署到其余实例，直到剩下最后一批实例为止.至此，最后一批实例终止.此部署策略可确保将失败的部署的影响限制在单批实例中，并使您的应用程序可以在正在进行的部署期间以最大容量提供流量.
Rolling with additional batch – starts by deploying your application code to a single batch of newly created EC2 instances. Once the deployment succeeds on the first batch of instances, the application code is deployed to the remaining instances in batches until the last batch of instances remain. At this point the last batch of instances is terminated. This deployment policy ensures that the impact of a failed deployment is limited to a single batch of instances and enables your application to serve traffic at full capacity during an ongoing deployment.
滚动–首先将您的应用程序代码部署到一批现有的EC2实例中.一旦在第一个批次上成功部署，就将应用程序代码分批部署到其余实例.此部署策略可确保将失败的部署的影响限制为单个批处理.但是，由于在部署过程中没有创建新实例，因此您的应用程序可以降低容量来提供流量服务(即:在部署过程中的任何给定时间，单批实例都无法使用).
Rolling – starts by deploying your application code to a single batch of existing EC2 instances. Once the deployment succeeds on the first batch, the application code is deployed to the remaining instances, in batches. This deployment policy ensures that the impact of a failed deployment is limited to a single batch. However, since no new instances are created during the deployment, you application can serve traffic at a reduced capacity (i.e.: a single batch of instances are out of service at any given time during the deployment).
这篇关于在AWS中滚动，滚动其他批处理与不可变部署之间有何区别?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！