You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears that the Gatekeeper is checking with MongoDB on every request to see if a particular key is valid. This would seem like something that should be cached temporarily in Redis on each router node to reduce request latency and the load on MongoDB. Even caching for a minute or so would make a huge difference for a high volume API. Thoughts?
The text was updated successfully, but these errors were encountered:
Yeah, this is one of those optimizations that's been on my mind for a while, but it's never quite happened. This has already been implemented in the experimental Lua revamp (#86), and it's actually a bit better there, since the cache is in local shared memory (rather than requiring a connection to Redis). That being said, we could certainly look at this kind of caching in the current Node implementation depending on the timeframe of the Lua work.
It appears that the Gatekeeper is checking with MongoDB on every request to see if a particular key is valid. This would seem like something that should be cached temporarily in Redis on each router node to reduce request latency and the load on MongoDB. Even caching for a minute or so would make a huge difference for a high volume API. Thoughts?
The text was updated successfully, but these errors were encountered: