3
다중 컨테이너 시스템 작업. 나는 탄력있는 콩팥과 ECS의 장단점을 평가했다. this과 같은 많은 질문이 있는데, ECS는 EB와 비교했을 때 컨테이너에 대한보다 정밀한 제어 기능을 갖추고 있지만 나열되어 있지는 않습니다. 내 관점에서 그들 사이의 차이점은 다음과 같습니다.멀티 컨테이너 고정 장치 용 탄산 콩 줄기 ECS 대
+--------------------------------------------+--------------------------------------------------+
| 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. |
+--------------------------------------------+--------------------------------------------------+
세 번째 요점은 확실하지 않습니다. 내가 틀렸다면 나를 바로 잡으십시오. 이 둘 사이에 다른 점이 있으면 알려주십시오.