Closed lucifercr07 closed 1 month ago
I can take this up @lucifercr07
Dependent on #729
@ayushsatyam146 assigned, thanks for contributing. Please let me know if any other details required.
@ayushsatyam146 PRs have been merged now, please let me know if any other details required.
Thanks, I'm currently working on wrapping up one more issue. I'll work on this as soon as I'm done there.
@ayushsatyam146 were you be able to start on this?
Hi @lucifercr07 I just started working on this today. I'll raise a PR by Tomorrow
Hi @lucifercr07 added PR for this at https://github.com/DiceDB/playground-mono/pull/17
Hello @ayushsatyam146,
There has been no activity on this issue for the past 5 days. It would be awesome if you keep posting updates to this issue so that we know you are actively working on it.
We are really eager to close this issue at the earliest, hence if we continue to see the inactivity, we will have to reassign the issue to someone else. We are doing this to ensure that the project maintains its momentum and others are not blocked on this work.
Just drop a comment with the current status of the work or share any issues you are facing. We can always chip in to help you out.
Thanks again.
Closing, merged as part of: https://github.com/DiceDB/playground-mono/pull/17
Description
DiceDB Playground is an interactive platform that allows users to experiment with DiceDB commands in a live environment, similar to the Go Playground. Users will be able to submit and execute commands directly through a web interface. The initial implementation will focus on enabling users to search for and trigger commands.
For more details about DiceDB playground you can check here.
After implementing the global rate limiter, it needs to be integrated into the
/command
API to evaluate each incoming request against the rate limit. Additionally, the response should include headers to inform clients about their current rate limit status, similar to GitHub's rate-limiting headers.The rate limiter should not apply to
/search
requests. However, for all other command requests, it should count each request and return detailed rate-limiting headers in the response.Note: Implementation will be part of DiceDB playground backend repo.
Details
/command
API.429 Too Many Requests
response./search
endpoint should be excluded from rate-limiting.Tasks
/command
API.429 Too Many Requests
responses./search
requests are not affected by the rate limiter.