Skip to content

[FEATURE] Enable CDN + Browser Caching for /api/v1/boards #389

Description

@sanaderi

Endpoint

GET /api/v1/boards


Problem

The /api/v1/boards endpoint is heavily used across multiple pages:

  • Home page
  • Search page
  • Other core pages

Currently, it is not effectively cached at the CDN level (Cloudflare), even though the data is highly static and typically changes only once per week.

This leads to:

  • Unnecessary backend load
  • Repeated identical requests for the same data
  • Higher latency for global users
  • Missed opportunity for edge caching performance gains

Endpoint Characteristics

  • Data is mostly static
  • Updates approximately once per week
  • Safe for shared caching across all users
  • No user-specific response expected

CDN (Cloudflare)

  • Cache response at edge
  • Serve cached responses for repeated requests
  • Return cf-cache-status: HIT on cache hits
  • Suggested TTL: 1 hour to 24 hours depending on update frequency

Browser

  • Allow short-term caching
  • Suggested TTL: 5–10 minutes

Suggested Response Headers

Cache-Control: public, max-age=300, s-maxage=86400


Expected Benefits

  • Reduced backend and database load
  • Faster response times for users globally
  • Improved scalability under high traffic
  • Reduced repeated identical requests across pages
  • Better performance for core application flows

Notes

  • Ensure endpoint does not depend on user authentication or cookies
  • Avoid sending Authorization header for this endpoint
  • Use cache invalidation or TTL strategy when boards are updated

Priority

High (core shared data used across multiple pages)

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Projects

Status
Todo

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions