Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Caching of API Keys on Router Nodes #111

Closed
darylrobbins opened this issue Feb 20, 2015 · 2 comments
Closed

Caching of API Keys on Router Nodes #111

darylrobbins opened this issue Feb 20, 2015 · 2 comments
Milestone

Comments

@darylrobbins
Copy link
Contributor

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?

@GUI
Copy link
Member

GUI commented Feb 23, 2015

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.

@GUI
Copy link
Member

GUI commented Nov 29, 2015

Key caching is performed in the v0.9 release.

@GUI GUI closed this as completed Nov 29, 2015
@GUI GUI added this to the v0.9 milestone Nov 29, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants