AWS Batch vs. HCL Workload Automation

More appropriate if you have a tech group that can use more of the AWS Batch rather than one or 2 things. It works great for me, but there was a huge learning curve the first week of using it. Now, I love it - and I hope to dig deep into other parts not just S3.

Incentivized

• 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

Incentivized

• Jobs monitoring dashboards are not matured
• Documentation and support is something which can be improved
• Sometime i faced the slow response or slow in performance i would say

Incentivized

Key advantages include cost-effectiveness through dynamic resource provisioning and the use of spot instances. It auto-scales to meet workload demands, allowing easy job submission via the AWS Management Console or SDKs. It integrates seamlessly with other services like S3 and CloudWatch. It features automatic retries for failed jobs. It allows for a custom computing environment tailored to specific needs

Incentivized

We wanted to start everything on a scale & with fewer resources to manage the underlying infrastructure.

Incentivized

• Overall over business is able to save the cost
• Saved our times to improve the existing process
• Able to integrate with other applications as well, so that is plus point

Incentivized