-1

I have a Java task scheduler that runs approximately 6 hours per day on AWS. I'm considering two deployment options and seeking advice on which one is more suitable for my use case:

Option 1: AWS Batch(Fargate Compute Environment) with EventBridge Scheduler

Option 2: AWS Fargate with Scheduler

I would like to know the pros and cons of each option to make an informed decision. Any insights or recommendations are greatly appreciated. Thank you!

Sivaram Rasathurai
  • 5,533
  • 3
  • 22
  • 45
  • 2
    Are you using AWS Batch already? Do you need the features of AWS Batch? Both of your solutions use the same scheduler (EventBridge) and the same compute environment (Fargate), one just has the extra features of AWS Batch, while the other uses regular ECS. – Mark B Jul 25 '23 at 15:22
  • Hey Mark B, currently we are doing some poc to check whether which one is fit for requirment. Our simple scheduler doesnt need any complex tracking. Based on your input, i beleive the cost for running the scheduler is same ryt – Sivaram Rasathurai Jul 25 '23 at 15:41
  • 1
    The price would be exactly the same either way, since they are both running on Fargate. – Mark B Jul 25 '23 at 15:53
  • 1
    I tend to agree that if your needs are simple then just use EB + Fargate. If you are finding that tasks do need retry capability, then look to Batch. Another case would be when you need to balance a limited set of resources across a few different types of jobs, then Batch's fair share scheduling may be good to look at. – Angel Pizarro Aug 04 '23 at 18:41

1 Answers1

-1

AWS batch vs AWS ECS (Fargate) To decide about wich one you will use, schedule mechanism is not an important feature.

https://stackshare.io/stackups/aws-batch-vs-aws-fargate#:~:text=With%20AWS%20Fargate%2C%20you%20no,%22Containers%20as%20a%20Service%22.

Jordi Tanta Diaz
  • 38
  • 4