Need advice about which tool to choose?Ask the StackShare community!
AWS Lambda vs IronWorker: What are the differences?
What is AWS Lambda? 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.
What is IronWorker? High-Scale Async Task Processing. IronWorker provides the muscle for modern applications by efficiently isolating the code and dependencies of individual tasks to be processed on demand. Run in a multi-language containerized environment with streamlined orchestration, IronWorker gives you the flexibility to power any task in parallel at massive scale.
AWS Lambda and IronWorker can be categorized as "Serverless / Task Processing" tools.
Some of the features offered by AWS Lambda are:
- Extend other AWS services with custom logic
- Build custom back-end services
- Completely Automated Administration
On the other hand, IronWorker provides the following key features:
- Containerized Environment
- High-Scale Processing
- Flexible Scheduling
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 Lambda
- No infrastructure126
- Cheap80
- Quick67
- Stateless57
- No deploy, no server, great sleep46
- AWS Lambda went down taking many sites with it9
- Extensive API5
- Event Driven Governance5
- Easy to deploy5
- Auto scale and cost effective4
- VPC Support3
- Integrated with various AWS services1
Pros of IronWorker
- Ease of configuration0
- Great customer support0
- Fully on-premise deployable0
- Cloud agnostic0
- Language agnostic0
- Can run Docker containers0
Sign up to add or upvote prosMake informed product decisions
Cons of AWS Lambda
- Cant execute ruby or go5
- Can't execute PHP w/o significant effort0
Cons of IronWorker
Sign up to add or upvote consMake informed product decisions
What is AWS Lambda?
What is IronWorker?
Need advice about which tool to choose?Ask the StackShare community!
What companies use AWS Lambda?
What companies use IronWorker?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with AWS Lambda?
What tools integrate with IronWorker?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+47
+43
+26
+23
+42