Implement distributed session management

[RUKAYAT-CODER]

Session management across multiple instances.

Acceptance Criteria:

• Redis session store
• Session serialization
• Cross-instance session access
• Session timeout management

[obswrld]

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

Distributed session management is a critical infrastructure concern for any backend that runs across multiple instances. Without a shared session store, users get logged out unpredictably depending on which instance handles their request — Redis solves this elegantly and I'm confident implementing it correctly.
Relevant experience:

Actively contributing to open source through the Stellar Wave Program across multiple repos
Strong NestJS backend experience — recently resolved agri-fi #156 which involved deep work inside a NestJS backend including auth guards, JWT strategy, middleware, and request lifecycle
Familiar with Redis as a session store — understand the serialization/deserialization pattern, TTL-based timeout management, and cross-instance key access
Experience with the full auth flow in NestJS — JWT strategy, Passport guards, user entity — which directly overlaps with session management concerns
SYNCRO #482 — worked extensively with auth hooks and session state on the frontend side, giving me a full-stack view of how sessions need to behave end to end

My approach:

Install and configure @nestjs/cache-manager with cache-manager-redis-store
Implement a Redis-backed session store with proper serialization
Add session timeout management via Redis TTL
Ensure cross-instance access works by keying sessions on a shared identifier
Write tests covering session creation, retrieval across instances, expiry, and serialization

This is a well-defined issue and I'm ready to deliver it cleanly before the deadline.
Ready to start immediately upon assignment.
@rinafcode/teachLink_backend

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

[drips-wave]

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

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

[drips-wave]

This issue has been completed by @obswrld as part of the Stellar Wave Program's 5th Wave 🥳

😎 @obswrld: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.