Need advice about which tool to choose?Ask the StackShare community!
AWS Batch vs AWS Lambda: What are the differences?
Developers describe AWS Batch as "Fully Managed Batch Processing at Any Scale". It enables developers, scientists, and engineers to easily and efficiently run hundreds of thousands of batch computing jobs on AWS. It dynamically provisions the optimal quantity and type of compute resources (e.g., CPU or memory optimized instances) based on the volume and specific resource requirements of the batch jobs submitted. On the other hand, AWS Lambda is detailed as "Automatically run code in response to modifications to objects in Amazon S3 buckets, messages in Kinesis streams, or updates in DynamoDB". AWS Lambda is a compute service that runs your code in response to events and automatically manages the underlying compute resources for you. You can use AWS Lambda to extend other AWS services with custom logic, or create your own back-end services that operate at AWS scale, performance, and security.
AWS Batch and AWS Lambda belong to "Serverless / Task Processing" category of the tech stack.
When adding a new feature to Checkly rearchitecting some older piece, I tend to pick Heroku for rolling it out. But not always, because sometimes I pick AWS Lambda . The short story:
- Developer Experience trumps everything.
- AWS Lambda is cheap. Up to a limit though. This impact not only your wallet.
- If you need geographic spread, AWS is lonely at the top.
Recently, I was doing a brainstorm at a startup here in Berlin on the future of their infrastructure. They were ready to move on from their initial, almost 100% Ec2 + Chef based setup. Everything was on the table. But we crossed out a lot quite quickly:
- Pure, uncut, self hosted Kubernetes — way too much complexity
- Managed Kubernetes in various flavors — still too much complexity
- Zeit — Maybe, but no Docker support
- Elastic Beanstalk — Maybe, bit old but does the job
- Heroku
- Lambda
It became clear a mix of PaaS and FaaS was the way to go. What a surprise! That is exactly what I use for Checkly! But when do you pick which model?
I chopped that question up into the following categories:
- Developer Experience / DX 🤓
- Ops Experience / OX 🐂 (?)
- Cost 💵
- Lock in 🔐
Read the full post linked below for all details
Pros of AWS Batch
- Scalable2
- Containerized2
Pros of AWS Lambda
- No infrastructure127
- Cheap82
- Quick69
- Stateless57
- No deploy, no server, great sleep47
- AWS Lambda went down taking many sites with it9
- Event Driven Governance6
- Auto scale and cost effective5
- Extensive API5
- Easy to deploy5
- VPC Support4
- Integrated with various AWS services2
Sign up to add or upvote prosMake informed product decisions
Cons of AWS Batch
- More overhead than lambda1
- Image management1
Cons of AWS Lambda
- Cant execute ruby or go5
- Can't execute PHP w/o significant effort0
Sign up to add or upvote consMake informed product decisions
What is AWS Batch?
What is AWS Lambda?
Need advice about which tool to choose?Ask the StackShare community!
What companies use AWS Batch?
What companies use AWS Lambda?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with AWS Batch?
What tools integrate with AWS Lambda?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+47
+43
+26
+23+42