ProjectTech4DevAI / ProjectTech4DevAI/kaapi-backend
Redis Caching
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 18
- Forks
- 10
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 14
Description
Is your feature request related to a problem? Please describe.
Right now every request goes straight to our database, which slows things down and can overload it when traffic spikes.
Describe the solution you'd like
Add Redis as a simple in-memory cache for things we fetch a lot—like user sessions, config settings, and common API responses or use Application level caching. On each call, check Redis first. If the data’s there, return it. If not, pull from the source, stash it in Redis with a short expiry, and send it back.
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 names no files, tests, or entry points. Start by locating the request and database-access paths for user sessions, configuration, and common API responses, then determine how Redis and expiry should be integrated. Done means repeated reads check Redis first, misses fetch and cache the source data with a short expiry, and the behavior is covered for the selected use cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, redis
- Domain
- backend, databases, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100