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.

Sign up for GitHub

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

Jump to bottom

Endpoint Throttling #139

Open
toastercup opened this issue Jul 28, 2015 · 0 comments
Open

Endpoint Throttling #139

toastercup opened this issue Jul 28, 2015 · 0 comments
Labels
infrastructure performance security
Milestone
Open Source

Comments

@toastercup
Copy link
Member

If Cortex is going to serve more than its internal users (especially if it's going to be open sourced), it needs endpoint protection, in the form of per-client request throttling.

Some questions to answer:

  • What should the default throttle rate be?
  • Certain trusted applications, like A&R, will be throttled significantly less by Cortex, so that it (A&R, or the trusted application) can handle its own rate limiting. What should the trusted application rate be?
@toastercup toastercup self-assigned this Jul 28, 2015
@toastercup toastercup added this to the Open Source milestone Jul 28, 2015
@toastercup toastercup removed their assignment Aug 13, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
infrastructure performance security
Projects
None yet
Milestone
Open Source
Development

No branches or pull requests
1 participant
@toastercup