CDN EdgeCache
Caching static/semi-static content at CDN edge nodes — cache-control headers, purge strategy.
Why we need this / what value this brings
Serves static/semi-static content from a location physically close to the user, cutting both latency and origin load.
When to use this
Content that's the same for most/all users and doesn't change on every request (listing pages, images, static assets).
How to use or implement this
Set explicit Cache-Control headers per content type, and have an intentional purge/invalidation path for when content does change.
Research questions
- What's actually cacheable on Localz's storefront (service listing pages) vs must stay dynamic (availability, pricing)?
Empty folder — drop notes, links, and findings here as you research.