Redis Caching Layer

[RUKAYAT-CODER]

Description

Overview

No distributed caching.

Background

Database load is too high.

Specifications

Add Redis caching.

Tasks:

• Add Redis client
• Add cache decorators
• Add invalidation logic

Impacted Files:

• src/cache/redis/*.ts

Labels: backend, cache, priority-high

Acceptance Criteria

Redis caching implemented

🙌Contribution Guidelines:

Assignment required before PR submission
Timeframe: 48-72 hours
PR description must include: Close #issue no
Star the repo⭐
For more context, please refer to the backend README 🚀

[David-patrick-chuks]

@David-patrick-chuks has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

Hi Maintainer,
I’ve reviewed the issue description and I’m comfortable with the scope and requirements. I’ll ensure the solution is clear, consistent, and easy to integrate.
Happy to take this on once assigned.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @David-patrick-chuks to this issue.

[jadonamite]

@jadonamite has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

Hi maintainer can I work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @jadonamite to this issue.

[rosemary21]

@rosemary21 has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

I’d like to work on this issue because adding a proper caching layer is one of the most impactful ways to improve system scalability and stability. Right now, the absence of distributed caching means the database is likely handling repeated read-heavy workloads that could be served much more efficiently through Redis. That kind of inefficiency becomes especially painful as traffic grows, often leading to higher latency, increased DB contention, and reduced overall system throughput.

What makes this task interesting is that it’s not just about “adding Redis”—it’s about designing a correct caching strategy: deciding what to cache, how long to cache it, and most importantly how to invalidate it safely. Cache invalidation is where most real-world bugs happen, so getting that right is critical for correctness.

Relevant experience:

I’ve implemented distributed caching layers using Redis in backend systems to reduce database load and improve response latency for high-traffic endpoints.
I’m familiar with designing cache-aside and write-through patterns, including tradeoffs between consistency and performance.
I’ve built TypeScript-based backend caching abstractions, including reusable cache decorators that transparently handle get/set logic without polluting business code.
I’ve implemented cache invalidation strategies tied to database mutations, ensuring stale data is not served after updates.
I understand failure modes in caching systems (cache stampede, stale reads, partial invalidation) and how to mitigate them using locking, TTL tuning, or request coalescing.
I’ve worked with async backend architectures where caching must be non-blocking and safe under concurrent load.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @rosemary21 to this issue.

[yusstyle]

@yusstyle has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

hello can i work on this please

ℹ️ Repo Maintainers: To accept this application, review their application or assign @yusstyle to this issue.

[drips-wave]

Congratulations, @David-patrick-chuks! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

🧑‍💻 @David-patrick-chuks: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊