Why AWS Batch is Blessing for some and curse for others
Use Cases and Deployment Scope
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



