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."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."
"We appreciate the simple use of containers within this solution, it makes managing the containers quick and easy."
"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."
"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."
"Fargate itself is a stable product. We are quite satisfied with its performance."
"The solution is highly scalable."
"Lambda has improved our organization by making it possible to transform data."
"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."
"It enables the launch of thousands of instances simultaneously,"
"The installation and configuration of the solution is straightforward."
"The utilization of containers is particularly beneficial in overcoming the size limitations imposed on Lambda functions which not only allows us to work around these constraints but also contributes to the improvement and maintenance of our code."
"It is my preferred product, as it provides me with source code within the solution."
"We are building a Twitter-like application in the boot camp. I have used Lamda for the integration of the post-confirmation page in the application. This will help you get your one-time password via mail. You can log in with the help of a post-confirmation page. We didn’t want to setup an instance specifically for confirmation. We used the Lambda function so that it goes back to sleep after pushing up."
"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."
"We faced challenges in vertically scaling our workload."
"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 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."
"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."
"I would like to see the older dashboard instead of the newer version. I don't like the new dashboard."
"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."
"Another challenge I've noticed is that there is a limit to the environment variables such as the 4 KB limit. Although, the advice is to use parameters or other things to store the details when the limit has exceeded the data, this adds additional intensity to the application. If the size limits for environment variables can be revealed, it would be helpful. Even if we have to pay for it, at least we would know that we are not dealing with latency. So, I would like to see the size of the environment variables increased."
"My engineers work with it on a daily basis. I just don't have enough depth of knowledge about what kinds of edge cases they may have tried and found lacking. There may be some issues with some language support at one point or another because we couldn't get the underlying libraries in there. A lot of what we do is either in JavaScript, Python, or some of the non-compiled languages. I'm not sure if we've ever tried building a C# solution, for instance, in Lambda or a Java solution in Lambda. It doesn't mean those aren't its capabilities. I would rather refer to my engineers for where the boundaries are."
"The product needs some updating as far as ease-of-customization and configuration opportunities to work with solutions outside of the cloud."
"Lambda has limitations on the amount of memory you can use and is not a good solution for long running processes."
"I have seen some drawbacks with certain integrations."
"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 could make the process of integration easier."
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 "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.