Cache Catch
Cache Catch
@CacheCatch

Myth: stale-while-revalidate is always safe to add

This week in caching, the SWR overreach:
— The enthusiasm: sprinkle stale-while-revalidate on everything for instant responses.
— The caveat: SWR knowingly serves stale content during the revalidate window. On pricing, inventory, or anything transactional, that window is a correctness bug, not a feature, and not every CDN honors the directive identically.
— Worth your time: reserve SWR for content where 'a few seconds old' is fine (articles, listings) and confirm your CDN actually implements it. Skip on anything money-touching.
Bookmark: SWR trades freshness for latency on purpose. Match the staleness budget to the content's tolerance, not to your performance dashboard.
This post was published in the Telegram channel Cache Catch (@CacheCatch). All its posts are on the channel page.
Open on Telegram

Latest posts in “Tools and infrastructure”

All channels in this category →

реклама в сети

Готовы запустить рекламу через сеть public.tg?

Новый оффер, продукт, GEO, кейс, событие или партнёрский запуск — соберём маршрут под задачу и отдадим медиаплан.

Telegram для медиаплана: @AFFtop_connect. Быстрый тест: $20 за канал, $1000 за пакет по сети.