Telemetry edge Stale-While-Revalidate caching headers across API routes #40
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What to build
Configure edge caching headers across dynamic Next.js API routes (
/api/hotspots,/api/tmat,/api/daops) to enable Stale-While-Revalidate caching at the CDN edge. Deliver sub-25ms telemetry responses to clients while refreshing data asynchronously in the background.Technical specifications
src/app/api/hotspots/route.tssrc/app/api/tmat/route.tssrc/app/api/daops/route.tsCache-Control: public, s-maxage=600, stale-while-revalidate=120.Vary: Accept-Encoding.Acceptance criteria
/api/hotspotsreturnCF-Cache-Status: HITorREVALIDATED.Authoritative Specifications & Reference Documentation
docs/ARCHITECTURE.mdIssue 27: [Backend] Telemetry edge Stale-While-Revalidate caching headers across API routesto [Backend] Telemetry edge Stale-While-Revalidate caching headers across API routes[Backend] Telemetry edge Stale-While-Revalidate caching headers across API routesto Telemetry edge Stale-While-Revalidate caching headers across API routesClosed as completed in main (edge SWR caching headers active across /api/hotspots, /api/tmat, /api/weather, /api/health).