RealDevSquad / RealDevSquad/website-backend
Remove the cached response from memory
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 74
- Forks
- 276
- Avg merge
- 1d 26m
- Merged PRs (30d)
- 14
Description
Description:
Currently we are caching our api response using custom in-memory module.
- This module does not remove the cached response when the expiry time is crossed. This results in memory leaks.
- There should also be a logic implemented to decide which response can be removed when the specified memory limit is reached.
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
The issue does not name files or tests; start by locating the custom in-memory caching module and the code that stores API responses. Trace expiry handling and the memory-limit path. Done means expired responses are removed and a defined eviction rule handles the configured memory limit without retaining stale entries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- api, backend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100