There is the class DeterministicLoadBalancer. This class is reposible for deterministic routing of request. It uses header X-InstanceId or last used used server to implement sticky session.
The issue is in the order of taken actions to process the request. If the request contains a token (the user could be detected) it always call caching service, even the value is not used there.
The impact:
- more I/O and performance degradation for authenticated request
- it could failed when Caching service is down (even the call is not needed)
There is the class DeterministicLoadBalancer. This class is reposible for deterministic routing of request. It uses header
X-InstanceIdor last used used server to implement sticky session.The issue is in the order of taken actions to process the request. If the request contains a token (the user could be detected) it always call caching service, even the value is not used there.
The impact: