Microsoft планирует вставлять рекламу в игры

➡️ Читайте на сайте: https://aff.top/blog/microsoft-planiruet-vstavliat-reklamu-v-igry

🧠 Ещё больше инсайтов → в канале AFF.top

Myth: more cache layers always means faster
This week in caching, the layering fallacy:
— The claim: stack page cache + object cache + CDN + browser cache and speed compounds.
— The correction: each layer adds an invalidation surface; a stale object cache can poison your fresh page cache, so a miss now costs a multi-layer rebuild instead of one.
— Worth your time: audit which layer actually owns the TTL for a given URL before adding another. Two coherent layers beat four that fight over the same key.
Bookmark: map your stack as a dependency tree, not a pile. The bottom layer's staleness window caps everything above it.

This week in caching: private browser cache vs shared CDN cache

The header nuance that causes the most cache bugs:

— Cache-Control: private means only the user's browser may store it — correct for logged-in dashboards. A CDN must skip it.
— public opens it to shared caches (CDN, proxies) — correct for anonymous pages.
— The killer: s-maxage overrides max-age for shared caches only. So you can tell the CDN 'cache 1 hour' while telling browsers 'cache 1 minute' — long edge life, fresh-ish clients, no header conflict.

Classic outage: serving a logged-in page as public and leaking one user's cart to everyone behind the CDN. Always pair user-specific responses with private AND a Vary on the auth cookie.

Bookmark: MDN's Cache-Control reference — keep the private/public/s-maxage section open while you debug.