Our primary use of ECS is to host all our services in the cloud. We work in the legal sector, and our workloads are often deployed on Fargate containers or Azure containers to abstract the hardware.

EC2 makes scaling horizontally incredibly easy, especially when working under the ECS service. Nowadays, I almost never need to create instances of virtual machines because most workloads can be deployed on Fargate containers. This abstraction of hardware reduces the need to think about it. 

My costs are reduced. Working with ECS and Fargate doesn't require saving processing units for idle services. Previously, using EC2 required keeping entire virtual machines running, however, Fargate eliminates this cost. ECS also allows for horizontal scalability with thresholds that can be configured for CPU or memory.

There is an issue where, in some situations, I need to scale up by observing both CPU and memory usage of containers, yet under the current options available at Amazon, this is not possible. I have to choose between monitoring CPU or memory to scale my solution. Not every software is built for deployment as a container service, although the current architecture trend is changing this.

I host everything in the cloud, and I have over ten years of experience. I use EC2 as a hosting technology and have been using it for a long time.

My services running on ECS are also on Azure Container Service. I have never experienced any flicker or downtime. These are highly available services. It's very stable.

ECS and Fargate make horizontal scalability very easy. I rate the scalability a ten out of ten. It allows for easy scaling, especially with ECS service configurations.

The AWS Support is incredible. They always invite us for meetings to showcase new solutions. I have a very good relationship with AWS, Microsoft, and GCP for support. AWS provides the best support, followed by Microsoft, and then Google.

Positive

Setting up ECS is simple, although there are some tricks involved. I usually have to define private and public networks and bind all related services. It's easy but not super straightforward. I had to repeat the process two or three times before I could teach others how to configure it.

Hosting services on Fargate reduces our processing costs since we don't need to keep virtual machines running for workloads anymore. This results in cost reductions.

AWS pricing is very competitive compared to Azure and cheap compared to Google. For some services, such as hosting databases, Google is really expensive.

On a scale of one to ten, I rate ECS a ten out of ten. It's an incredible service, and I prefer it over Kubernetes. I suggest checking the integration of software for deployment in a serverless environment. Some software can be challenging to deliver this way.