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

Worry about Rate Limit #111

Open
niehusst opened this issue Dec 2, 2020 · 0 comments
Open

Worry about Rate Limit #111

niehusst opened this issue Dec 2, 2020 · 0 comments
Labels
bug Something isn't working

Comments

@niehusst
Copy link
Owner

niehusst commented Dec 2, 2020

The Search API endpoint is rate limited based on Client ID rather than what user is making the request, so all simultaneous users will be subject to the same rate limit.

From docs it's not clear at what point the app would be rate limited; the only thing I could do is wait out rate limit errors instead of returning error to user.

"If Web API returns status code 429, it means that you have sent too many requests. When this happens, check the Retry-After header, where you will see a number displayed. This is the number of seconds that you need to wait, before you try your request again."

This seems like a potentially big scaling problem.

@niehusst niehusst added the bug Something isn't working label Dec 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant