I have one doubt that when we say we can save correlation Id in local hashmap as well, then one instance's local hashmap is accessible to other instances?
Local hashmap will apply to the instance only. This way only the instance that has a particular ID will be able to process a message. It's a cheaper way to handle correlation IDs without going for a distributed solution. I personally feel distributed is a more robust approach but costs can be a concern.
What an amazing Article Saurabh!
I have one doubt that when we say we can save correlation Id in local hashmap as well, then one instance's local hashmap is accessible to other instances?
Thanks for the wonderful feedback Hitesh.
Local hashmap will apply to the instance only. This way only the instance that has a particular ID will be able to process a message. It's a cheaper way to handle correlation IDs without going for a distributed solution. I personally feel distributed is a more robust approach but costs can be a concern.
Azure Service Bus is among my top 3 favorites. Simply put, Saurabh.
Thanks for the shoutout!
Thanks Raul!
In Asyn. request-response, Is correlation id will be same for retries or partial payment ? Or a new id will be generated??
Btw very informative article;)
Thanks for the feedback Shashi.
It's a new correlation id per request.
new correlation id for every request used for retries or partial payment
Thanks!
Azure Service Bus is what an amazing tech, used for many solutions already!
A great post my friend, and many thanks for the mention!
Thanks for the superb feedback Daniel!