RealDevSquad / RealDevSquad/website-backend
[RFC] Idempotent Requests Setup
Open
Nobody has claimed this yet.
backend
enhancement
- Dominant language
- JavaScript
- Stars
- 74
- Forks
- 276
- Avg merge
- 1d 26m
- Merged PRs (30d)
- 14
Description
- We have some APIs like clearing cache etc. which a user should not be able to call as it costs us and probably the user will be also be costed with our crypto.
- To prevent excess firing of these API calls there has to be some setup to limit the API calls.
- Idempotent Requests is one of the solution, more context on this here https://github.com/Real-Dev-Squad/website-my/pull/79#discussion_r906656607
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked pull-request discussion for the additional context on idempotent requests. Identify which costly APIs need protection and define the request-limiting behavior and completion criteria before locating the relevant backend entry points; the issue names no files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100