What advice do you have for others considering AWS Fargate?

I recommend using AWS Fargate as it offers serverless computing capabilities with integration into load balancing, making it a good and beneficial solution. I'd rate the solution six out of ten.

Before using AWS ECS Fargate, identify the business use case to determine whether a serverless solution is needed. Also, consider your scaling mechanism and security best practices to avoid misconfigurations that may impact cost and performance. I'd rate the solution eight out of ten.

I'd rate the solution eight out of ten.

For customers who use AWS to organize their application environment, leveraging AWS's computing capabilities can lead to cost optimization. They can use the AWS cloud platform model to access services on demand. Overall, I rate the solution a ten out of ten.

AWS Fargate can be used to run almost any type of application. It requires an application container, such as an application server container, a backend container for a database like MySQL, and a frontend container, which could be a web server like Apache. Multiple containers must be deployed simultaneously, and configuring these multiple containers within a single cluster can be somewhat complex. I recommend the tool for the initial event; you can try it out. If you feel it's reliable, you can consider adding it on. However, if you feel that it will mainly depend on your current application, you may need to evaluate it further. It is easy to learn. Overall, I rate the solution an eight out of ten.

The maturity you have in deploying serverless capabilities is crucial. For example, if your process takes less than 15 minutes, then you should consider AWS Lambda or other cloud function services. If your process may take longer than that, then Fargate is the way to go, especially when you are starting to deploy. Your first goal is to provide scalability to your business, particularly to your commercial areas. Once you achieve scalability, you can then focus on cost efficiency. If cost becomes a significant factor as you scale up, you might consider managing a Kubernetes cluster with an auto-scaling service to simplify Kubernetes management. When you need that level of scalability, cloud services like Fargate or even Lambda may not provide the cost efficiency you require. That's my current perspective on this. Overall, I would rate the solution a ten out of ten.

On a scale from one to ten, I would rate it around eight. I would recommend using the product based on the specific workloads they are dealing with. For instance, if they have strict sub-second performance requirements, I might not suggest it. The decision depends on their specific requirements, and I would advise accordingly.

In terms of process documentation and speed, it really depends on what how many CPUs and memory you put in and whether you get adequate speed. For me, it's more than enough. All those functions are primitive functions. They mostly don't need big CPUs and stuff. You just break stuff into many microservices. AWS Fargate has many valuable services. It does the job with minimal trouble. It's very observable. You can see what's going on and you have logs. You have everything. You can troubleshoot it. It's affordable and it's flexible. I would rate AWS Fargate a ten.

I would rate this solution a seven out of ten.

I rate AWS Fargate an eight out of ten.

What's suitable for potential users depends on their company's IT capability. For a small company, it's best to engage a consultant service for help. For example, we could consult others on the solution in my previous outsourcing company. It wouldn't have been a very good one if we did it ourselves. My current company is very big, and we have the know-how here, and it's easier for us to make the decision. On a scale from one to ten, I would give AWS Fargate an eight.

Everything in this solution works like a charm. I'd rate it as ten out of ten.