RealDevSquad / RealDevSquad/website-backend
Caching `/users` and `/users/*` API or users data
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 74
- Forks
- 276
- Avg merge
- 1d 26m
- Merged PRs (30d)
- 14
Description
Feature request
Many features/sub-projects require RDS users data, and users data don't change that often.
Our read to Firesotre for requesting each users data has a cost attached to it, so caching the user data be it at db level or API level
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 locating the /users and /users/* API entry points and tracing their reads for user data. Clarify whether the cache belongs at the database or API level, how updates invalidate it, and how success will be measured by reducing repeated Firestore reads without serving outdated data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- api, backend, databases, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100