-1

I have a use-case where the consumer service (ServiceA) is calling my service (ServiceB) multiple times. ServiceB is AWS EC2-based. I can create a Batch API for the same which will enable ServiceA to put all the requests in a list and send them to ServiceB in a single request. Rest all processing at ServiceB remains same.

I just want to compare based on the cost saving that will happen either on Service A or Service B's end if we start to use Batch version.

My understanding is that if ServiceB would be a AWS Lambda based service or if I would have been making use of API Gateway in ServiceB then we would incur less costs as Lambda or API-gateway charges on request basis as well. What can be the cost benefits in an EC2 service which is always up?

ask
  • 149
  • 1
  • 8

0 Answers0