Re:How we reduced deployment times by 95%
by otterley on Wednesday August 28, 2019 @02:51PM
(#20822785)
That sounds different from the usual way customers perform an ECS deployment, which is to replace the task definition of the ECS Service with a new one and let the control plane manage it. Only a single API call is needed, and the control plane can launch replacement tasks pretty quickly itself.
[ Parent
| on HN ]
Re:How we reduced deployment times by 95%
by ahmcb on Wednesday August 28, 2019 @03:56PM
(#20823468)
We don't actually call the startTask API ourselves, but when we tell an ECS service (using cloudformation) to use a new task definition (which is basically just a new ECR image tag), ECS calls startTask and various other APIs on our behalf.
Re:How we reduced deployment times by 95%
by otterley on Wednesday August 28, 2019 @04:35PM
(#20823728)
That is true. FWIW, as an experiment I built a 50-node ECS cluster and launched 4000 tasks on it. I couldn't build a single service with 4000 tasks due to soft limits, so I built 4 services with 1000 tasks each (nginx, 256MB, 128 CPU units). No load balancer.
Overall task replacement time was about 15 minutes -- which is pretty respectable, in my view. Obviously not as fast as doing a hot code swap, though. Tradeoffs abound.