Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEAT] Implement API Caching for Read-Heavy Endpoints #1305

Open
Dan-Gaya opened this issue Feb 28, 2025 · 0 comments
Open

[FEAT] Implement API Caching for Read-Heavy Endpoints #1305

Dan-Gaya opened this issue Feb 28, 2025 · 0 comments

Comments

@Dan-Gaya
Copy link

Implement API Caching for Read-Heavy Endpoints

Description

Repeated requests to static data endpoints (FAQs, help topics) cause unnecessary database load. Frequent API calls for static data can be optimized using caching.

Solution

Use Redis or an in-memory cache for frequently accessed endpoints.

Affected Endpoints

GET /api/v1/faqs
GET /api/v1/help-center/topics

Tasks

  • Identify read-heavy endpoints (e.g., /api/v1/faqs, /api/v1/help-center/topics).
  • Implement caching using Redis or an in-memory store.
  • Set cache expiration rules to prevent stale data.
  • Write tests to ensure cache efficiency.

Acceptance Criteria

  • Cached responses reduce load on the database.
  • Expired cache data is refreshed correctly.
  • Tests validate cache functionality.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants