We performed a comparison between AWS Fargate and AWS Lambda based on real PeerSpot user reviews.
Find out in this report how the two Compute Service solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI.
"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."
"If you create your deployment with a good set of rules for how to scale in, you can just set it and forget it."
"The most valuable feature of AWS Fargate is its ease of use."
"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."
"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."
"I like their containerization service. You can use Docker or something similar and deploy quickly without the know-how related to, for example, Kubernetes. If you use AKS or Kubernetes, then you have to have the know-how. But for Fargate, you don't need to have the know-how there. You just deploy the container or the image, and then you have the container, and you can use it as AWS takes care of the rest. This makes it easier for those getting started or if you don't have a strong DevOps team inside your organization."
"We appreciate the simple use of containers within this solution, it makes managing the containers quick and easy."
"Lambda is the preferred compute option because of on-demand cost. We don't have to provision any hardware beforehand. We don't have to provision the capacity required for the services because it is serverless."
"The initial setup of AWS Lambda is very straightforward and quick."
"I like the pay-for-what-you-use feature. This is the main reason why we use AWS Lambda. I don't have to manage servers; I just have to configure Lambda and expose it to an API gateway."
"The tool scales automatically based on the number of incoming requests."
"It is my preferred product, as it provides me with source code within the solution."
"The solution offers good performance."
"I think the most valuable feature is the agility of the solution."
"AWS Lambda is interlinked with CloudWatch. When we have any errors we can directly go there and check the CloudWatch logs. Additionally, we can run it very fast and we can increase the RAM size and other components."
"AWS Fargate could improve the privileged mode containers. We had some problems and they were not able to run."
"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."
"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 the older dashboard instead of the newer version. I don't like the new dashboard."
"We would like to see some improvement in the process documents that are provided with this product, particularly for auto-scaling and other configuration tools that are a bit complicated."
"We faced challenges in vertically scaling our workload."
"The product could make the process of integration easier."
"The automation with other Amazon products could be better."
"We need to better understand Lambda for different scenarios. We need some joint effort between Amazon and the users to have the users identify how they can really leverage Lambda. It's not about Lambda itself; it's about the practice, the guidance. There needs to be very good documentation. From the user perspective, what exists now is not always enough."
"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."
"I would like to see more integration with other platforms."
"It can be a bit difficult to switch between accounts when creating services for customers."
"Lambda has limitations on the amount of memory you can use and is not a good solution for long running processes."
"Amazon doesn't have enough local support based in our country."
AWS Fargate is ranked 6th in Compute Service with 8 reviews while AWS Lambda is ranked 1st in Compute Service with 70 reviews. AWS Fargate is rated 8.6, while AWS Lambda is rated 8.6. The top reviewer of AWS Fargate writes "Offers serverless capabilities, self-managed, simplifies ease of use and integrates with other AWS services". On the other hand, the top reviewer of AWS Lambda writes "An easily scalable solution with a variety of use cases and valuable event-based triggers". AWS Fargate is most compared with Amazon EC2 Auto Scaling, Amazon EC2, AWS Batch, Oracle Compute Cloud Service and Apache Spark, whereas AWS Lambda is most compared with AWS Batch, Amazon EC2 Auto Scaling, Apache NiFi, Apache Spark and Google Cloud Dataflow. See our AWS Fargate vs. AWS Lambda report.
See our list of best Compute Service vendors.
We monitor all Compute Service reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
