Calling Caching service from Gateway using micro-services #4422
Description
This issue is bases on #4408.
Currently the Gateway calls caching service to store revoked tokens. It is done by calling Gateway itself and it is responsible for routing to a Caching service instance.
It doesn't respect Zowe instance topology, so any service could be called, even it is not on the same system. Calling a local instance should be preferable.
Even this is the local logic there is no implementation of retry approach. It should use in theory retry logic from the routing, but it is not used because there are used other methods than GET. For purposing of storing revoked tokens it is possible to retry a call (twice stored revoked token doesn't change the state).
The best implementation for micro-services should be used a client with loadbalancer (ideally using local instance as prefferable one).