-
-
Notifications
You must be signed in to change notification settings - Fork 114
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
[FEATURE] Add Rate Limiting to APIs for Database-Backed Endpoints #417
Comments
Upstash is one of the good option here. |
is this issue or security feature resolve with npm package express-rate-limit??? const limiter = rateLimit({ |
@manzil-infinity180 express-rate-limit limits all traffic but it seems like the Upstash limiter only limits endpoints that interact with redis |
@kairblarson it make sense |
Ive been looking into it more and it seems like the upstash rate limiter leverages a redis cache so its not feasable unless we add redis. I then tried to use the express-rate-limit package but I dont think it works with nextjs however I did find a more traditional work around in this article here: https://kittygiraudel.com/2022/05/16/rate-limit-nextjs-api-routes/ I tried to implement it myself but could not figure out the exact typing |
hello @kairblarson, |
@madjed-hue this looks promising, ill look into it thank you! |
Hi @rohitdasu if the issue is not solve i want to contribute it |
Sure |
@rohitdasu i don't see is this assign it to me |
@rohitdasu can you assign this to me so I can work |
Assigned you @MrBlackGhostt |
Plz Assign issue me? |
assigned you. let us know if you need anything :) |
@parasvekariya26 are you still working on this? please let us know |
Description
This issue aims to enhance the performance and security of our APIs by implementing rate limiting for endpoints that involve database operations. Rate limiting is crucial to prevent abuse, ensure fair usage, and protect our infrastructure from potential threats.
Let us discuss first which service is best for implementing rate limiting!
The text was updated successfully, but these errors were encountered: