Calling Caching service from Gateway using micro-services
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 92
- Forks
- 81
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 46
Description
This issue is bases on https://github.com/zowe/api-layer/pull/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).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing PR 4408 and the Gateway's current calls to the caching service, then inspect the existing routing and load-balancing implementation. The change is complete when caching requests prefer an instance on the local system and revoked-token storage has retry coverage for repeatable calls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend-api-design, distributed-systems
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100