workos
Add caching functionality/pathways for token validation
Every time we validate a session token, it makes a request to WorkOS's infra to get the same value from their systems to validate the token. On our end, we see each validation operation adds ~200ms to each request that performs a token check. Usually the key used for authenticity verification changes very infrequently so it's something that can be cached. The SDK could cache the key in a singleton on the server and use that and validate using the cached key optimistically. If the authenticity check fails, then it can call the endpoint to see if the verification key changed at WorkOS as a fallback, if it turns out to be a cache miss, then check the token and at the same time update the cache.
This should improve perf greatly on our end.
I just noticed that WorkOS has the option to set an inactivity timeout value when it comes to session management. Adding caching COULD break the enforcement of this policy depending on how inactivity is tracked. How does inactivity work?