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

AWS Batch vs AWS Lambda comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jan 12, 2025

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 Batch
Ranking in Compute Service
6th
Average Rating
9.0
Number of Reviews
4
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 February 2025, in the Compute Service category, the mindshare of AWS Batch is 20.3%, up from 19.6% compared to the previous year. The mindshare of AWS Lambda is 20.8%, down from 26.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Compute Service
 

Featured Reviews

Larry Singh - PeerSpot reviewer
User-friendly, good customization and offers exceptional scalability, allowing users to run jobs ranging from 32 cores to over 2,000 cores
The main drawback to using AWS Batch would be the cost. It will be more expensive in some cases than using an HPC. It's more amenable to cases where you have spot requirements. So, for instance, you don't exactly know how much compute resources you'll need and when you'll need them. So it's much better for that flexibility. But if you're going to be running jobs consistently and using the compute cluster consistently for a lot of time, and it's not going to have a lot of downtime, then the HPC system might be a better alternative. So, really, it boils down to cost versus usage trade-offs. It's going to be more expensive for a lot of people. In future releases, I would like to see anything that could help make it easier to set up your initial system. And besides improving the GUI a little bit, the interface to it, making it a little bit more descriptive and having more information at your fingertips, so if you could point to the help of what the different features are, you can get quick access to that. That might help. With most of the AWS services, the difficulty really is getting information and knowledge about the system and seeing examples. So, seeing examples of how it's being used under multiple use cases would be the best way to become familiar with it. And some of that would just come with experience. You have to just use it and play with it. But in terms of the system itself, it's not that difficult to set up or use.
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

"We can easily integrate AWS container images into the product."
"AWS Batch's deployment was easy."
"AWS Batch manages the execution of computing workload, including job scheduling, provisioning, and scaling."
"There is one other feature in confirmation or call confirmation where you can have templates of what you want to do and just modify those to customize it to your needs. And these templates basically make it a lot easier for you to get started."
"Lambda allows you to focus on the code itself."
"The serverless computing feature eliminates the need to manage servers, provision, or scale."
"The basic feature that I like is that there is no server installation. It also has good support for various languages, such as Java, .NET, C#, and Python."
"What I like most about AWS Lambda is that it's very easy to deploy."
"You can spin up anything instantly without any investment."
"The automation feature is valuable."
"The tool scales automatically based on the number of incoming requests."
"They have the built-in IDE, so everything happens without integration issues."
 

Cons

"The solution should include better and seamless integration with other AWS services, like Amazon S3 data storage and EC2 compute resources."
"The main drawback to using AWS Batch would be the cost. It will be more expensive in some cases than using an HPC. It's more amenable to cases where you have spot requirements."
"When we run a lot of batch jobs, the UI must show the history."
"AWS Batch needs to improve its documentation."
"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."
"AWS Lambda is a bit difficult to set up if someone doesn't know how to code."
"Lambda can only be used in one account; there's no possibility to utilize it in another account."
"Amazon doesn't have enough local support based in our country."
"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."
"There were some timeout issues with AWS Lambda as the options provided didn't suit our business cases."
"The product could make the process of integration easier."
"The user-friendliness of the solution could be improved."
 

Pricing and Cost Advice

"AWS Batch's pricing is good."
"AWS Batch is a cheap solution."
"The pricing is very fair."
"AWS Lambda is not expensive for micro testing but is expensive if used for long deployment or long services."
"AWS Lambda's cloud version isn't expensive, and I'd rate its pricing as five out of five."
"Lambda is a good and cheap solution and I would recommend it to those without a huge payload."
"The solution is part of the AWS subscription model that is paid annually."
"The solution follows a pay-as-you-go licensing model, which results in cost savings."
"Price-wise, AWS Lambda is a five out of ten."
"AWS Lambda is cheap."
"AWS Lambda is a cheap solution."
report
Use our free recommendation engine to learn which Compute Service solutions are best for your needs.
837,501 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
27%
Computer Software Company
10%
Manufacturing Company
7%
Government
6%
Educational Organization
67%
Financial Services Firm
8%
Computer Software Company
4%
Manufacturing Company
3%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

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 Batch?
AWS Batch manages the execution of computing workload, including job scheduling, provisioning, and scaling.
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.
What needs improvement with AWS Lambda?
Having a better preview would be helpful. Sometimes, if my Lambda code is too big, it can be inconvenient as I'm unable to see my code when it exceeds a certain size. AWS has a limit, like a three-...
 

Comparisons

 

Also Known As

Amazon Batch
No data available
 

Overview

 

Sample Customers

Hess, Expedia, Kelloggs, Philips, HyperTrack
Netflix
Find out what your peers are saying about AWS Batch vs. AWS Lambda and other solutions. Updated: January 2025.
837,501 professionals have used our research since 2012.