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.
"We appreciate the simple use of containers within this solution, it makes managing the containers quick and easy."
"If you create your deployment with a good set of rules for how to scale in, you can just set it and forget it."
"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."
"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."
"The most valuable feature of AWS Fargate is its ease of use."
"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."
"The most valuable features are event-based triggers. They're really good for a reactive style when you want things to happen as soon as something else happens."
"The ability to scale up and down very quickly helps because we can maintain our system performance and business at a low cost."
"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."
"It is easy to use."
"By using Lambda, we can use Python code and the Boto3 solution."
"I have found all of the features valuable. It's an easy and cheap solution."
"The valuable feature of AWS Lambda is the ease of coding. It is easier to code using the solution."
"The main area for improvement is the cost, which could be lowered to be more competitive with other major cloud providers."
"AWS Fargate could improve the privileged mode containers. We had some problems and they were not able to run."
"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."
"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."
"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."
"I would like to see the older dashboard instead of the newer version. I don't like the new dashboard."
"Amazon doesn't have enough local support based in our country."
"I think that perhaps Lambda could explore its functionality more."
"The first time Lambda is started up, it takes some time to spin up an instance for serving the consumer requests. AWS has been trying to solve this in a variety of ways but have not yet managed to do so."
"Lambda would benefit from a debugging feature as well."
"AWS Lambda should support additional languages."
"The feature to attach external storage, such as an S3 or elastic storage, must be added to AWS Lambda. This is its area for improvement."
"The setup was pretty complex because there were many steps. For me, it was complex because I was somewhat new at it. It could be easier for someone who has done it a bunch of times. I just found that it was a very dense user experience. There's a lot going on during setup."
"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.
