Amazon Elastic Container Service (Amazon ECS) vs. Google Cloud Run

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.

Incentivized

For prototyping or quick deployment, it works as an interesting step between containerized deployment (Kubernetes) vs pure Compute Engine (raw servers). It's not well suited for Kubernetes shops, or for teams that would prefer more hardware control.

Incentivized

• 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.

Incentivized

• Can easily run our apps in a docker in Google Cloud Run which has simplified code testing and deployment.
• Can easily scale and does not have any problem when put under a large load.
• Has all the necessary services so you don't need to look for other cloud solutions.
• Pay as you go model so only pay for that you've used and how long you've used it.

• A cleaner container service road map
• It would be. nice to have more AI recommended cluster reductions
• The UX could use some simplification

Incentivized

• Some more use case/ manual/notes to be available on internet
• Cost can be minimized.
• Not able to use in mobile phone

Incentivized

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.

Incentivized

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.

Flexibility of features snd customzing options tha optimized the large process and make it on the the go to reuse the same process in multiple deployments ot rollouts

Incentivized

• 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.

Incentivized

• Improved production deployment times by 50%
• The error analysis time was reduced by 30%, thanks to its logging and monitoring system.
• The rollback is almost immediate, as it easily allows reverting to a previous stable version.

Incentivized