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.
"If you create your deployment with a good set of rules for how to scale in, you can just set it and forget it."
"We appreciate the simple use of containers within this solution, it makes managing the containers quick and easy."
"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."
"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 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."
"The most valuable feature of AWS Fargate is its ease of use."
"It's a serverless solution which is the best feature. It helps us because it offers free aspects. From the infrastructure perspective, it helps us manage costs. There is no overhead of estimating how much infrastructure we're going to need. We can focus on building the business functionality that we want to build."
"The solution is scalable."
"The solution integrates well with API gateways and S3 events via its AWS ecosystem."
"The support from AWS Lambda is very good, they are responsive."
"AWS Lambda is a stable solution."
"AWS Lambda is itself serverless, and it is connected to the API gateway, and you can directly call the API through the API gateway and connect through AWS Lambda."
"Technical support has been great in general."
"I have found all of the features valuable. It's an easy and cheap solution."
"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."
"The main area for improvement is the cost, which could be lowered to be more competitive with other major cloud providers."
"We faced challenges in vertically scaling our workload."
"AWS Fargate could improve the privileged mode containers. We had some problems and they were not able to run."
"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."
"If it is a specific ETL process or a long-term one, then AWS Lambda is not a good option."
"Lambda could be improved in the sense that some of the things done with Lambda function take some time. So the performance could be better and faster."
"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."
"The price in general could always be better."
"The support team does not know how to implement and build the solution."
"My opinion is that the integration could be improved in this solution. We have had some difficulties integrating the EC2 module, but we found a solution for that by ourselves."
"The running time of AWS Lambda runs fine. It takes around five minutes but it would be great if that time could be extended."
"AWS Lambda could be improved by increasing the size of the payload. Also, sometimes Lambda doesn't implement well for bigger solutions."
AWS Fargate is ranked 6th in Compute Service with 7 reviews while AWS Lambda is ranked 1st in Compute Service with 70 reviews. AWS Fargate is rated 8.8, while AWS Lambda is rated 8.6. The top reviewer of AWS Fargate writes "Efficiently auto-scales and good performance". 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.
