Redis cache layer for hot endpoints

[Asheeyah23]

Background

/assets/popular and /search get hit hard; caching is the easy win.

What to build

A Redis layer with per-route TTL, opt-in via config.

Key files

• src/cache/redis.ts (new)

Acceptance criteria

• Cache-hit and cache-miss paths tested
• Honors X-No-Cache header

Drips Wave · Complexity: Intermediate · 150 points

---

Security / Ops (W059–W060)

---

Required: Before submitting, join the contributor Telegram so your work can be tracked and counted toward the Stellar Wave: https://t.me/+fxHXq8f1SwlkZDBk

[edehvalentine236-jpg]

@edehvalentine236-jpg has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello maintainer, I'm Valentine. I would like to work on this issue. Kindly assign.

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

[Asheeyah23]

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

I'd like to take on this issue. A Redis cache layer will dramatically reduce DB load on hot endpoints with minimal implementation risk.
My plan:

Redis Client: Create src/cache/redis.ts wrapping ioredis with typed get/set/invalidate helpers and configurable TTL per route (POPULAR_TTL=60s, SEARCH_TTL=30s).
Middleware: Fastify preHandler that checks Redis before hitting DB — cache hit returns immediately, miss fetches and populates cache with route-specific TTL.
X-No-Cache: Bypass cache and force fresh fetch when X-No-Cache: 1 header present, still populates cache on response.
Opt-in Config: Enable per route via config flag cache: { enabled: true, ttl: 60 } — zero impact on unconfigured routes.
Tests: Mock ioredis — assert cache hit skips DB call, cache miss populates Redis, X-No-Cache bypasses correctly.

I'm experienced with Redis caching patterns and Fastify middleware. Ready to implement this. Please assign this to me.

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

[githoboman]

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

helllo would love to work on this

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

[collinsezedike]

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

GM Ebube, let me help you with this issue.

Here's my plan:

• src/cache/redis.ts: a middleware/wrapper that checks Redis for a cached response keyed on route + query params, with a configurable per-route TTL
• Config-driven opt-in per route, starting with /assets/popular and /search
• When X-No-Cache is present, skip the cache lookup entirely and also skip writing the fresh response back to cache, so a debug request doesn't pollute the cache for everyone else
• Tests covering: cache miss populates Redis and returns the live response, cache hit returns the cached response without hitting the underlying handler, and X-No-Cache bypasses both read and write

Happy to start as soon as I'm assigned.

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

[Caneryy]

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

Hello! Can I work on this issue please?

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

[drips-wave]

Congratulations, @githoboman! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @githoboman: 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 🌊