[server] - Add Redis Caching Layer for Frequently Read Endpoints

[dark-sarge]

Location: server/src/utils/cache.ts

Description

High-traffic read endpoints such as GET /api/trades (marketplace listing) will be queried repeatedly by many users simultaneously. Without a caching layer, every request hits PostgreSQL, increasing latency and database load. A Redis-backed cache with TTL-based invalidation should be added for expensive read paths.

Acceptance Criteria

• ioredis is added as a dependency and a shared Redis client is initialised from a REDIS_URL environment variable.
• A cache.get<T>(key) and cache.set<T>(key, value, ttlSeconds) utility is created in server/src/utils/cache.ts.
• GET /api/trades (marketplace listing) caches the full response for 30 seconds, keyed by the serialised query params.
• Cache entries are invalidated when a new trade is created or an existing trade's status changes.
• Cache reads are logged at debug level; cache misses are logged at info level with the key.
• If Redis is unavailable the server falls back to direct database reads and logs a warn — it does not crash.

---

[yusufmuhammadayodeji-netizen]

@yusufmuhammadayodeji-netizen has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Ready to contribute. Please assign me the issue.

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

[Max347bot]

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

Hi Maintainer! I'm a senior developer with experience building high-quality, production-ready software. I'd love to take on this issue and deliver a clean, well-tested solution that aligns with the project's standards. Please assign it to me—I'm ready to get started and contribute effectively.

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

[drips-wave]

Congratulations, @Max347bot! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

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