Try our new research platform with insights from 80,000+ expert users

AWS Fargate vs AWS Lambda comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

AWS Fargate
Ranking in Compute Service
2nd
Average Rating
8.6
Reviews Sentiment
7.5
Number of Reviews
17
Ranking in other categories
No ranking in other categories
AWS Lambda
Ranking in Compute Service
1st
Average Rating
8.4
Reviews Sentiment
7.5
Number of Reviews
83
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of April 2025, in the Compute Service category, the mindshare of AWS Fargate is 14.7%, down from 17.7% compared to the previous year. The mindshare of AWS Lambda is 21.0%, down from 23.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Compute Service
 

Featured Reviews

Subrata Mukherjee - PeerSpot reviewer
Boost demand response with cost-efficient serverless architecture
We are a venture builder company, and if we select AWS for our product. Our design is based on a serverless architecture model. ECS Fargate is the most convenient way in terms of scalability, integration, and cost control Thanks to the serverless model and easy integration features, a few…
Wai L Lin O - PeerSpot reviewer
A serverless solution with easy integration features
We use AWS Lambda because it provides a solution for our needs without requiring us to manage our infrastructure. With the tool, we only pay for the resources we use. Additionally, it is straightforward to implement and integrates with other services like API Gateway. The tool's serverless nature has had the most significant impact on our workflow. I find it particularly attractive because it eliminates the need for managing servers. In my previous experience, managing upgrades and updates was quite challenging. The solution's integration process with other AWS services was relatively easy. We primarily use AWS services such as EventBridge for scheduling processes and log management.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"Fargate's integration with other AWS services is really good."
"It allows for focusing on applications instead of managing infrastructure."
"The most valuable feature of Fargate is that it's self-managed. You don't have to configure your own clusters or deploy any Kubernetes clusters. This simplifies the initial deployment and scaling process."
"AWS Fargate is an easy-to-use tool to simplify setup. You only pay for the resources you use. If you need to quickly create, delete, or scale applications without managing resources like EC2 instances, Fargate is the best service to use."
"AWS Fargate automatically scales to meet demand, making it ideal for applications with variable workloads."
"We appreciate the simple use of containers within this solution, it makes managing the containers quick and easy."
"Fargate itself is a stable product. We are quite satisfied with its performance."
"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."
"The solution is highly scalable."
"Because AWS Lambda is serverless, server configuration is not required, and we can run it directly anywhere."
"They have the built-in IDE, so everything happens without integration issues."
"AWS Lambda is entirely stable."
"This product is easy to use."
"The solution is scalable."
"I have found all of the features valuable. It's an easy and cheap solution."
"We moved our users into the Amazon Cognito pool, so it helps us to standardize our security practices, approaches, etc. We can customize Lambda for authentication to integrate it with API Gateway and other services."
 

Cons

"AWS Fargate needs improvement in terms of setup complexity."
"I would like to see the older dashboard instead of the newer version. I don't like the new dashboard."
"The main area for improvement is the cost, which could be lowered to be more competitive with other major cloud providers."
"If there are any options to manage containers, that would be good. That relates more to the cost point. For example, over the next three months, I'll be making a comparison between solutions like CAST AI and other software-as-a-service platforms that offer Kubernetes management with an emphasis on cost reduction."
"Challenges include higher costs for smaller clients, limited control over underlying infrastructure customization, and potential latencies during task startup."
"As I have not worked with Fargate extensively, I do not have any specific improvements."
"Service computing is not as straightforward compared to other computing services. It requires more effort to use effectively."
"I heard from my team that it's not easy to predict the cost. That is the only issue we have with AWS Fargate, but I think that's acceptable. AWS Fargate isn't user-friendly. Anything related to Software as a Service or microservice architecture is not easy to implement. You're required to have DevOps from your side to implement the solution. AWS Fargate is just a temporary solution for us. When we grow to a certain level, we may use AKS for better control."
"I would like to see some better integration with other providers, like Cohesity, Druva, and others. I also think the Lambda interface could be better."
"I have seen some drawbacks with certain integrations."
"It currently requires manual user maintenance to upgrade and evaluate, and an automated provision for this would be beneficial."
"The solution should continue to streamline integrations with AWS services."
"Memory limitation is one of the weaknesses of AWS Lambda and as a result, we have to use several Lambda, instead of just one. Recently, I met with an Amazon employee, who is responsible for Lambda as a product. It appears Amazon has some plans with Lambda, so I don’t have to add something to the additional features."
"The product needs some updating as far as ease-of-customization and configuration opportunities to work with solutions outside of the cloud."
"Having a better preview would be helpful."
"What could be improved in AWS Lambda is a tricky question because I base the area for improvement on a specific matrix, for example, latency, so I'm still determining if I can be the judge on that. However, room for improvement could be when you're using AWS Lambda as a backend, it can be challenging to use it for monitoring. Monitoring is critical in development, and I don't have much expertise in the area, but you can use other services such as Xray. I found that monitoring on AWS Lambda is a challenge. The tool needs better monitoring. Another area for improvement in AWS Lambda is the cold start, where it takes some time to invoke a function the first time, but after that, invoking it becomes swift. Still, there's room for improvement in that AWS Lambda process. In the next release of AWS Lambda, I'd like AWS to improve monitoring so that I can monitor codes better."
 

Pricing and Cost Advice

"We would advise that this solution has a slightly-higher price point than others on the market. There is a free plan available for start-ups, but the free and lower range licensing models do not provide the full functionality."
"I rate the price of AWS Fargate a four out of five."
"The solution's price is average."
"The solution follows a pay-as-you-go licensing model, which results in cost savings."
"AWS Lambda's cloud version isn't expensive, and I'd rate its pricing as five out of five."
"The price of AWS Lambda is priced very low."
"The cost is based on runtime."
"AWS Lambda is not expensive for micro testing but is expensive if used for long deployment or long services."
"Lambda is a good and cheap solution and I would recommend it to those without a huge payload."
"The price of the solution is reasonable."
report
Use our free recommendation engine to learn which Compute Service solutions are best for your needs.
845,406 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
24%
Computer Software Company
13%
Government
8%
Comms Service Provider
7%
Educational Organization
70%
Financial Services Firm
7%
Computer Software Company
4%
Manufacturing Company
3%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about AWS Fargate?
The most valuable feature of Fargate is that it's self-managed. You don't have to configure your own clusters or deploy any Kubernetes clusters. This simplifies the initial deployment and scaling p...
What needs improvement with AWS Fargate?
The monitoring capabilities of AWS Fargate could be improved and made more robust. The error handling aspect sometimes causes issues and can get stuck during deployment, making the process not very...
What advice do you have for others considering AWS Fargate?
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...
Which is better, AWS Lambda or Batch?
AWS Lambda is a serverless solution. It doesn’t require any infrastructure, which allows for cost savings. There is no setup process to deal with, as the entire solution is in the cloud. If you use...
What do you like most about AWS Lambda?
The tool scales automatically based on the number of incoming requests.
What is your experience regarding pricing and costs for AWS Lambda?
AWS Lambda is cheaper compared to running an instance continuously. You only pay for what you use, making it cost-effective.
 

Comparisons

 

Overview

 

Sample Customers

Expedia, Intuit, Royal Dutch Shell, Brooks Brothers
Netflix
Find out what your peers are saying about AWS Fargate vs. AWS Lambda and other solutions. Updated: March 2025.
845,406 professionals have used our research since 2012.