Why AWS Batch is Blessing for some and curse for others
Use Cases and Deployment Scope
We encountered issues orchestrating long-running tasks in Lambda functions, as they have a limit of 15 minutes. We needed a solution that could be triggered from AWS Step Functions. Then we found yes it's a bit tedious to set up, has a steep learning curve but once that's passed you can easily run a 24 or 48 hours or other long-timed task without any issues, which helped our use case where needed to run a task which took 24 hours even with AWS Batch's Compute
Pros
- Easy to orchestrate and trigger jobs
- No time limit issues like lambda
- Multiple Jobs can be run in same single compute and job queue
- JOb queue can queue up task for parralled or serialization
Cons
- Steep Learning Curve
- Setting up jobs could be easy
- Giving roles access to compute environment is hard and confusing
Return on Investment
- Well compared to the cost of having multiple lambda's or some other custom solution working, it has has a postiive impact
- Helped in orchestrating the jobs, has saved time of developers
Usability
Other Software Used
Amazon CloudWatch



