<b>This week in caching: edge vs origin, the real trade-offs</b>
Where the cache lives changes everything downstream:
— <i>Edge caching personalized pages</i> — ESI and edge-side composition so logged-in users still get cached shells with dynamic holes punched in.
— <i>Cache key cardinality at the edge</i> — why caching by geo or device blows up your storage and hit rate simultaneously.
— <i>Origin shield</i> — the often-missed CDN layer that collapses requests so your origin sees one miss, not 200 PoPs worth.
— <i>Compute-at-edge isn't free caching</i> — when Workers/Lambda@Edge add latency instead of removing it.
Credits: Cloudflare and Fastly architecture docs.
Bookmark: the origin-shield explainer — single biggest origin-load win most teams haven't turned on.
Cache Catch
@CacheCatch
<b>This week in caching: edge vs origin, the real trade-offs</b>
Этот пост опубликован в Telegram-канале Cache Catch. Подписаться можно по ссылке: @CacheCatch.