I would recommend AWS Fargate to other people. My advice for people about AWS Fargate is to be aware of the cost of using this solution. On a scale of one to ten, I rate AWS Fargate a nine.
My team hasn't used AWS Fargate's capability for automatic scaling in our applications, even when they knew about it; they were very new to using these features. AWS Fargate's security features weren't the most important criteria or value we got from AWS Fargate. I would recommend AWS Fargate to others; I would use it myself if I were in a startup or a medium-sized team because of the simplicity it offers without having to manage Kubernetes clusters. As we started using Kubernetes, I found it complex and only justified when you have a larger team that can manage certified cloud architects and cloud engineers. For a small team, I would go blindly using AWS Fargate if I want to take advantage of containers in a scalable way. I rate AWS Fargate overall as 10 out of 10. I don't have any regrets using it. We have never had any problem using it, even when we used it with very basic knowledge of the cloud.
Software Engineering Manager – Digital Production Optimization at Yara International ASA
Real User
Top 5
Mar 10, 2025
I would recommend AWS Fargate as an alternative to AWS Lambda for running loads or hosting a service. It is a good service for keeping instances running, which minimizes initial latency. Overall, I give AWS Fargate a rating of eight out of ten.
AWS Fargate is easily manageable. We just need to create a cluster and focus on our infrastructure. Customers do not need to take downtime since everything is managed by AWS with no downtime. Overall, I would rate it as nine out of ten.
I rate Fargate ten out of ten. The most significant advantage is the unified configuration for all containers deployed by ECS, allowing seamless integration with services like OpenAI or Google Gemini and secure handling of access keys and secrets.
AWS & Azure DevOps Engineer at Cravita Technologies India Private Limited
Real User
Top 5
Oct 25, 2024
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.
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.
DevOps Engineer at a tech services company with 11-50 employees
Real User
Top 10
Apr 29, 2024
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.
AWS Cloud Architect at a tech services company with 1-10 employees
Real User
Dec 8, 2022
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.
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.
A new compute engine that enables you to use containers as a fundamental compute primitive without having to manage the underlying instances. With Fargate, you don’t need to provision, configure, or scale virtual machines in your clusters to run containers. Fargate can be used with Amazon ECS today, with plans to support Amazon Elastic Container Service for Kubernetes (Amazon EKS) in the future.
Fargate has flexible configuration options so you can closely match your application needs and...
Using AWS Fargate is becoming easier as the platform improves. On a scale of 1-10, I rate AWS Fargate a 7.
I would recommend AWS Fargate to other people. My advice for people about AWS Fargate is to be aware of the cost of using this solution. On a scale of one to ten, I rate AWS Fargate a nine.
My team hasn't used AWS Fargate's capability for automatic scaling in our applications, even when they knew about it; they were very new to using these features. AWS Fargate's security features weren't the most important criteria or value we got from AWS Fargate. I would recommend AWS Fargate to others; I would use it myself if I were in a startup or a medium-sized team because of the simplicity it offers without having to manage Kubernetes clusters. As we started using Kubernetes, I found it complex and only justified when you have a larger team that can manage certified cloud architects and cloud engineers. For a small team, I would go blindly using AWS Fargate if I want to take advantage of containers in a scalable way. I rate AWS Fargate overall as 10 out of 10. I don't have any regrets using it. We have never had any problem using it, even when we used it with very basic knowledge of the cloud.
I would recommend AWS Fargate as an alternative to AWS Lambda for running loads or hosting a service. It is a good service for keeping instances running, which minimizes initial latency. Overall, I give AWS Fargate a rating of eight out of ten.
AWS Fargate is easily manageable. We just need to create a cluster and focus on our infrastructure. Customers do not need to take downtime since everything is managed by AWS with no downtime. Overall, I would rate it as nine out of ten.
I rate Fargate ten out of ten. The most significant advantage is the unified configuration for all containers deployed by ECS, allowing seamless integration with services like OpenAI or Google Gemini and secure handling of access keys and secrets.
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.