Add Redis caching for session endpoints to improve performance

[shwetharbaliga]

Problem Statement

• Currently, every time the user refreshes their dashboard or checks session history, the backend fetches data directly from MongoDB.
• This increases response time and database load, especially when users frequently start, pause, or complete sessions.

Proposed Solution

• Add a Redis caching layer to temporarily store frequently accessed session data (/current, /history) for faster retrieval.

Implementation idea:

• Use ioredis or redis npm package.

• Cache key format: session:${userEmail}

• Set a TTL of 5–10 minutes.

• Invalidate cache whenever session data is created, updated, or deleted.

Alternatives Considered

• Using in-memory caching (e.g., node-cache) — but it wouldn’t scale across multiple backend instances.

• MongoDB indexing — helps query speed but doesn’t reduce repeated hits.

Additional Context

• This would improve user experience on dashboards and analytics pages, reducing API response times by 30–50% while easing database loa

[Nischay-loq]

@shwetharbaliga
I request that u assign this issue to me

[shwetharbaliga]

@Harshdev625 Please assign this issue to me

[Harshdev625]

@shwetharbaliga I think Redis implementation isn’t required here since the data is sent live and updated frequently — we’re mainly storing site data.

However, I have another repo where you can work with Redis:
🔗 https://github.com/Harshdev625/SDEverse

To discuss further, you can join my project Discord channels where we handle changes over meetings:

• SDEverse: https://discord.gg/AEjesXaT
• Time Machine: https://discord.gg/cJvRVDyR

@Nischay-loq I’d love for you to join as well — I can assign you some issues there.
Please join both Discord servers and ask about available issues in the #issues section.