Likelihood to Recommend Amazon Elastic Container Service (Amazon ECS) is well suited where you need the ease of managing the clusters by letting AWS do the stuff for you. Obviously, whenever you want to run the docker based workloads, it is always better to go for either AWS ECS or AWS EKS. If you are interested in staying at AWS only and don't want to be cloud-agnostic, then go for AWS ECS instead of AWS EKS. AWS ECS is cheaper than AWS EKS and also more managed by AWS and better integrated with other AWS services. If you want to run those workloads as serverless, then AWS ECS Fargate is the best option to go with. If you already have a
Kubernetes based setup that you want to migrate to AWS, then go for AWS EKS instead of AWS ECS.
Read full review You are going to be able to find the most resources and examples using Docker whenever you are working with a container orchestration software like Kubernetes. There will always some entropy when you run in a container, a containerized application will never be as purely performant as an app running directly on the OS. However, in most scenarios this loss will be negligible to the time saved in deployment, monitoring, etc.
Read full review Pros One of the biggest advantages is the flexibility to change underlying EC2 instances. As the traffic or demand increases, we can easily change EC2 instances without any issues. Amazon ECS APIs are extremely robust and one can start and stop containers by firing one post request only. So, it is not mandatory to keep the demo solutions up for every time. Just at the time of demo fire the command - make the container up and running - do the demo - down the container with API. A simple portal can control every container which helps non-technical (sales, marketing) to do the demo without keeping the solutions up for the entire time frame. Read full review Packaging of application to limit the space occupied Ease of running the application Provide multiple ways to handle the application issues and integration of different components like pipeline, ansible, terraform etc Read full review Cons A cleaner container service road map It would be. nice to have more AI recommended cluster reductions The UX could use some simplification Read full review Docker hub image retention policy can be relaxed Docker hub policies can be more developer friendly Docker CLI help section can be improved Image and container storage (local) management can be optimized Read full review Usability Very easy to use, great tutorials, documentation and cheat sheets out there to help you become a Docker Wiz
Read full review Reliability and Availability Haven't seen any outages, fatal/unrecoverable errors in my usage so far. Enough said.
Read full review Performance Docker Desktop. The CPU high usage is a known issue. Needs fixing. Otherwise, it is great overall. Would not use anything else still.
Read full review Support Rating Support is relatively good, although the documentation sometimes is lacking, as well as outdated in our experience, especially when we initiated the process of using this service. But once we found how to assemble things, we haven't really required support from anyone at AWS, the service works without problems so we haven't had the need to contact support, which speaks well of how ECS is built.
Read full review Alternatives Considered EKS is a
Kubernetes technology and you need to learn
Kubernetes and build a cluster before using it. So there's a learning curve here. ECS was easier to implement and simpler to have in our use case. It takes less time to run a workload and make it available.
Read full review The reason why we are still using Docker right now is due to that is the best among its peers and suits our needs the best. However, the trend we foresee for the future might indicate Amazon lambda could potentially fit our needs to code enviornmentless in the near future.
Read full review Scalability It is the only tool in our toolset that has not [had] any issues so far. That is really a mark of reliability, and it's a testimony to how well the product is made, and a tool that does its job well is a tool well worth having. It is the base tool that I would say any organisation must have if they do scalable deployment.
Read full review Return on Investment We achieved minimum downtime. The autoscaling kept the performance of the services great. We saved money by running the workloads on AWS ECS in Fargate mode by having different settings for different services to save on the hardware configuration side as well as having scheduled tasks. Read full review Reduces the number of virtual machine which impacted our quarterly billing Using docker with proxy we run multiple application on same port on same host. impact on billing is we have to provide docker training to the people who are working on it. Read full review ScreenShots