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

"AWS Batch manages the execution of computing workload, including job scheduling, provisioning, and scaling."
"AWS Batch's deployment was easy."
"We can easily integrate AWS container images into the product."
"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 is trigger-based, which means it only activates when accessed, ensuring cost savings."
"Because AWS Lambda is serverless, server configuration is not required, and we can run it directly anywhere."
"By using Lambda, we can use Python code and the Boto3 solution."
"AWS Lambda is a stable solution."
"The main features of this solution are the ability to integrate multiple AWS applications or external applications very quickly and organize all of them. Additionally, it is easy to use and you can run various programming languages, such as Python, Go, and Java."
"Some of the most valuable features are that it's easy to install and use. The performance is also good."
"AWS Lambda is entirely stable."
"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."
"AWS Batch needs to improve its documentation."
"When we run a lot of batch jobs, the UI must show the history."
"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."
"Lambda's dashboard could be more user-friendly and customizable. I want the dashboard to have more information to quickly identify what functions and events are running. Also, we want to be able to add more trigger points, push notifications, and events."
"The solution should continue to streamline integrations with AWS services."
"The price in general could always be better."
"AWS Lambda could improve by having no-code or low-code options because currently, you need to be able to write code well to use it."
"AWS Lambda has a limitation where the execution time is capped at 15 minutes per task. Increasing this time would allow for handling heavier tasks more efficiently."
"One area of improvement is to include support for more programming languages. AWS Lambda does not support a lot of programming languages. You have to write the Lambda functions in a certain programming language. We are using C++. My developer knows a couple of other languages. Python is his favorite language, but Python is not supported in AWS Lambda."
"There are sometimes issues following an update."
 

Pricing and Cost Advice

"The pricing is very fair."
"AWS Batch's pricing is good."
"AWS Batch is a cheap solution."
"Lambda is an affordable solution. They offer free requests every month and charge per the compute time. If you are working in a big organization, usually AWS offer a savings plan where you get approximately 70% discount on pricing."
"Its pricing is on the higher side."
"The price is expensive and is based on usage. The more users you have the higher the cost."
"AWS Lambda cost is pretty decent."
"AWS Lambda is not expensive for micro testing but is expensive if used for long deployment or long services."
"For licensing, we pay a yearly subscription."
"AWS Lambda is inexpensive."
"The solution is part of the AWS subscription model that is paid annually."
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.