| Table of Contents |
|---|
...
After a few iterations we settled on the following:
Cache keys are compound; comprised of 4 parts: <Method>|<PathPattern (or 'Path' if not defined)>|<X-Okapi-User-Id>|<X-Okapi-Token>
...
A PoC was evaluated by the Performance Task Force (PFT). That effort was tracked in PERF-113. In a test which simulated 8 concurrent users, the benefits seen during check-in/check-out were as follows:
...
- Port the token cache PoC to Okapi 4 - https://github.com/folio-org/okapi/tree/tokenCache
- Add metrics for tracking cache events (hits/misses/etc.) - https://github.com/folio-org/okapi/tree/tokenCache
- Re-test with this version of the PoC
- Create stories (OKAPI/MODAT) for the implementation of this optimization -
Jira Legacy server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODAT-86 Jira Legacy server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key OKAPI-890 - Sort out other implementation details - See Considerations above.