CODEWITHSUNDEEP
multithreadingweb-servicesasynchronouscallbackexecutorservice
pogo22
pogo22

Reputation: 147

Java ExecutorService for Async web service

We need to implement a Async web service.

We send the request for an account to server and it sends back the sync response with an acknowledgement ID. After that we get multiple Callback requests which contains that acknowldegment ID. The last callback request for an acknowledgement ID will contain a text(completed:true) in the response which will tell us that this is the last callback request for that account and acknowledgement ID. This will help us to know that async call for a particular account is completed and we can mark its final status. We need to execute this web service for multiple accounts. So, we will be getting callback requests for many accounts.

What is the optimal way to process these multiple callback requests coming for multiple accounts.

Please suggest an optimal way to implement requirement both memory and performance wise.

Upvotes: 4

Views: 1005

Answers (1)

duffymo
duffymo

Reputation: 308948

Let's be clear about one thing: HTTP is a blocking, synchronous protocol. Request/response pairs aren't asynch. What you're doing is spawning asynch requests and returning to the caller to let them know the request is being processed (HTTP 200) or not (HTTP 500).

I'm not sure that I know optimal for this situation, but there are other considerations:

  1. Use an ExecutorServiceThreadPool that you can configure. Make sure you have a prefix that lets you distinguish these threads from others.
  2. Add request task to a blocking dequeue and have a pool of consumer threads process them. You can tune the dequeue and the consumer thread pool sizes.
  3. If processing is intensive, send request messages to a queue running on another server. Have a pool of queue listeners process the requests.

You cannot assume that the callbacks will return in a certain order. Don't depend on "last" being "true". You'll have to join all those threads together to know when they're finished.

It sounds like the web service should have a URL that lets users query for status.

Upvotes: 2

Related Questions