-
Notifications
You must be signed in to change notification settings - Fork 424
feat: add inflight rate limiting documentation and improve tooling #2255
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
base: master
Are you sure you want to change the base?
Conversation
tricky42
commented
Jul 25, 2025
- Add comprehensive endpoint-based rate limiting documentation
- Document inflight request limiting for concurrent request protection
- Add protected endpoints table with rate limit types and actions
- Add Makefile help target and dev server target
- Update dependencies to latest minor versions
- Add comprehensive endpoint-based rate limiting documentation - Document inflight request limiting for concurrent request protection - Add protected endpoints table with rate limit types and actions - Add Makefile help target and dev server target - Update dependencies to latest minor versions
@vinckr / @Demonsthere review pls |
- Provides options for Enterprise and Growth customers to whitelist internal IPs for higher rate limits. | ||
- Balances security needs with the requirements of high-volume legitimate traffic. | ||
|
||
### Notes on rate limit rules | ||
### Types of endpoint-based protection | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think here we should keep the distinction of layers:
- Global CDN layer with Cloudflare
- Local Business logic layer with Envoy
The current proposal flattens that which i don't think is a good idea.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I intentionally chose not to disclose these "implementation" details, as they shouldn't affect the customer, and it also allows us the flexibility to modify the implementation without needing to update this documentation or notify the customers.