多集装箱码头用弹性豆杆与ECS的比较

Question

+--------------------------------------------+--------------------------------------------------+
|              Elastic Beanstalk             |                        ECS                       |
+--------------------------------------------+--------------------------------------------------+
| Natively support auto-scaling and load     | Auto-scaling can be done with                    |
| balancing. Has the ability to deploy       | some extra efforts. But other AWS resources      |
| other AWS resources along with the         | cannot be deployed with ECS.                     |
| containers.                                |                                                  |
+--------------------------------------------+--------------------------------------------------+
| Container definitions are written in       | Container definitions has to be written in a     |
| dockerrun.aws.json file. All the links     | separate task definition file. Scaling of the    |
| can be written here. This is more like     | container can be specified in                    |
| docker compose file.                       | service definitions.                             |
+--------------------------------------------+--------------------------------------------------+
| Scaling happens based on CloudWatch        | Here, we have a precise control to scale         |
| metric. But when a new instance is         | a particular task (container). This is more      |
| launched, the whole containers in          | like declarative. It does not take in to account |
| task definition file will be launched      | about the instances, it maintains the count of   |
| again (imperative), even though some       | tasks correctly. Scales based on the             |
| of the containers actually has no traffic. | CPU/Memory usage of a specific container.        |
+--------------------------------------------+--------------------------------------------------+

第三点我不太清楚。如果我错了就纠正我。如果这两者之间还有其他不同之处，让我知道。

Answer 1

第一点：如果您没有使用弹性Beanstalk，并且希望在应用程序中部署其他AWS资源，请创建一个CloudFormation模板，并使用CloudFormation变更集来启动、升级和拆除应用程序。

对于第三点，弹性Beanstalk使用AWS自动缩放特性，该特性仅在创建和删除EC2实例的级别上工作。因此，如果您使用的是弹性Beanstalk中的单容器/多容器环境，那么扩展将不仅仅是创建另一个容器，而是一个运行Docker的包含所有相同容器的整个EC2实例。自动缩放也可以在不使用弹性豆茎的情况下从云形成模板使用。它仍然只能在EC2实例级别上工作。

另一个选择是使用具有自动缩放功能的弹性Beanstalk，将环境设置为一个需要缩放的容器的容器docker，并将其他容器添加为AWS：：ECS：：Service自定义资源。例如，您的单个容器可以是处理繁重的前端，而另一个容器可以是共享数据存储。这样，您就可以从弹性Beanstalk获得很好的版本化/部署/滚动，但容器是单实例的（每个弹性Beanstalk环境）。