Index of every page on this site: llms.txt
All skills
proyecto26 avatar

/content-delivery

@228d57d
Run it yourself

This skill should be used when the user asks about a "CDN", "edge caching", "static asset delivery", "media / video delivery", "geo distribution of content" or "edge POP selection", "push vs pull CDN", "cache-control headers" / "TTL for static assets", "origin offload", or "origin shield". It gives the recipe for serving bytes from the edge close to users. Use it whenever a design serves images, video, JS/CSS, or downloads to a wide geography, or the origin is saturated by repeat reads of the same files, even if the user doesn't say "CDN".

Use this Skill: https://skilld.dev/gh/proyecto26/system-design-skills/content-delivery

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesprovidersazure.md

≈448 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Content delivery — Azure

Service mapping

  • Azure Front Door — the strategic choice: global anycast edge that combines CDN caching, TLS termination, path-based routing, and L7 load balancing / failover across origins in one product. Prefer it for new designs.
  • Azure CDN — classic pull CDN (Microsoft/edge network); simpler, caching-only. Note the older third-party (Verizon/Akamai) tiers are being retired — verify the current product against docs before designing around them.
  • Blob Storage / Static Website hosting — the usual static/media origin behind Front Door or CDN.
  • Traffic Manager — DNS-based geo/priority routing when you need pure DNS steering rather than an anycast edge (→ load-balancing).

When to pick which

Front Door when you want edge caching and global routing/failover/WAF together (most cases); plain Azure CDN only for caching with no routing needs; Blob Static Website + Front Door for a simple static site.

Limits / things that bite (verify against current docs)

  • Front Door caching rules decide query-string and header handling — default behavior may not cache as you expect; configure the cache key explicitly.
  • Purge propagation is not instant; prefer versioned URLs.
  • Front Door and classic CDN have different feature sets and pricing models — don't assume parity; rules engines differ.
  • Egress / routing costs are the dominant line; tiers vary by region.

Pitfalls

  • Designing around a retiring CDN tier — confirm the SKU is current.
  • Expecting Front Door's routing features from plain Azure CDN (it's caching-only).
  • Misconfigured cache key (forwarding all query strings) → low hit rate.
  • Lock-in via Front Door rules engine / WAF policies that don't port elsewhere.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts24d3 checks · Risk SAFE
  • Gen Agent Trust Hub24d

    The skill is a comprehensive architectural guide for designing Content Delivery Networks (CDNs). It consists solely of technical documentation and does not contain any executable code, external scripts, or malicious patterns.

  • Socket24d

    No alerts

  • Snyk24d

    Risk: LOW · No issues

Signed by skilld at 228d57d. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 weeks ago.

Activeupdated 4 weeks ago

README badge

README badge for proyecto26/system-design-skills/content-delivery