Handling Java RMI in AWS ASG

0

We have 2 services front end api service and a backend service. In order to get high tps we are using async calls.

  1. End user http call lands on one of the tomcat servers in frontend
  2. The frontend calls backend in Async with the context of the server ip and puts the request thread to sleep
  3. Once backend finishes the job it makes a callback to frontend using rmi with the server ip it got in context
  4. In the callback the original http thread is invoked.
  5. The invoked http request thread consumes the prepared data from cache and completes the response.

This was fine till we were in physical DC as we used to not scale or de-scale. With AWS ASG the server ip might not exist by the time backend service tries to make a callback. Due to this the request at the user end needs to get requests retried.

We want to get out of RMI here and still remain async. Would like to get any solutions for this

posta 2 anni fa46 visualizzazioni
Nessuna risposta

Accesso non effettuato. Accedi per postare una risposta.

Una buona risposta soddisfa chiaramente la domanda, fornisce un feedback costruttivo e incoraggia la crescita professionale del richiedente.

Linee guida per rispondere alle domande