QuorumWiki
Jugar

CDN

Responde cerca del usuario las páginas que se pueden cachear. El egress desde el edge cuesta menos.

Esta página aún no está traducida al español.

The CDN answers cacheable content at the edge, near the user, as Cloudflare does with its network of edge servers.

When to place it#

  • Place it when page views or video load your App Servers. See Cut the cloud bill. It unlocks with Content delivery.

  • Place it when egress is a large line in the Ledger.

  • Skip it for API reads, writes, logins and checkouts. A CDN does not cache them, so they always reach the origin.

How it works#

Place it right after Users. It takes every request kind, answers the anonymous share of page views and most video at the edge, and sends the misses and every other kind on to your origin. A logged-in page is not cacheable until Edge-side includes. It has no capacity limit and serves every region.

Egress from the edge costs less than egress from your App Servers, so a CDN also cuts the cloud bill once egress is billed. A longer TTL raises the hit ratio, and the Tiered caching Research lifts how much video the edge answers. See CDN and egress.

Options#

ControlValoresCuándo
TTL1 min / 5 min / 1 hSiempre
Purgar al desplegarMantener hasta el TTL / PurgarSiempre
Clave de cachéRuta, query y cookies / Ruta y query / Solo rutaSiempre
  • TTL: how long the edge keeps a page. A longer TTL raises the hit ratio, so raise it for pages that change rarely.

  • Purge on deploy: a release empties the edge, and the origin takes the misses while it refills. Without it the edge keeps serving the last release's pages until their TTL passes, so some users see old pages after a deploy.

  • Cache key: what makes two requests the same page. A key with the path, the query string, and the cookies shares nothing between users. Leaving out the query string or the cookie lifts the hit ratio. With Edge-side includes a logged-in page is cached, so a key without the cookie can serve one user's page to another. That is the Cached page leak incident, and users leave at once.

How it fails#

The CDN itself does not overload in the game. What goes wrong:

  • Every request pays the edge hop, including the misses that go on to the origin.

  • A short TTL lowers the hit ratio, and more traffic reaches your origin.

  • Without one, a DDoS or Traffic spike hits your App Servers in full. A CDN takes the cacheable part.

Cached page leak#

  • Signs: Users fall 5% at once, and one user's logged-in page reached another.

  • Do now: Nothing ends it early. It runs its course, 90 sim seconds in the catalog.

  • Prevent: Set Cache key on the CDN card to Path, query and cookies, so a personal page is never shared. The leak needs Edge-side includes and a key without the cookie.

Certificate expired#

  • Signs: The Certificate expired banner appears, and every request through the CDN fails, as through every other TLS Node.

  • Do now: Click Renew in the banner.

  • Prevent: Research Certificate automation and place a Secrets and Certificates Node, which renews the certificates before they run out.

Tips#

  • Pair it with Object Storage when you serve video.

  • Place a WAF after the CDN, so the WAF sees only the misses.

  • Raise the TTL when pages change rarely.

Reglas#

  • Cada copia adicional cuesta un 25% más que la anterior.
  • Al venderlo se devuelve el 50% de lo que costó su última copia.
  • Tiene un solo tamaño.

Funciona con#

Usuarios, Almacenamiento de objetos, Función serverless, WAF, Función edge, Secretos y certificados

Investigación siguiente#

Cuando tengas Entrega de contenido, estas Investigaciones se apoyan en ella.

Caché por niveles, Computación en el edge, Edge-side includes

Seguridad#

Estas vulnerabilidades pueden afectarle. Aplica el parche antes de que acabe el plazo de gracia.

  • CVE-2026-1337, CVSS 9.8

Términos de ingeniería#