Yes as a caller we need to know that the request is completed.
My app is actually waiting for a response to move to another step of the transaction.
With the current timeout problem, we are losing complete transactions since we have no sucessfull response from the API.
Yes as a caller we need to know that the request is completed.
My app is actually waiting for a response to move to another step of the transaction.
With the current timeout problem, we are losing complete transactions since we have no sucessfull response from the API.
Is this a public end user making the call or is it an internal business person?
It's a public user, and through our service he reach the external API to make the transaction, and by its end we need yo present him with a response
In this case, you might want to look into the Saga pattern?