SuperAPI AI Directory

cdn-caching-and-edge-acceleration-patterns

General & other

View repository

Updated 10-16 06:43

About this skill

CDN Caching And Edge Acceleration Patterns

Use When

  • Global users require low-latency content delivery
  • Origin load or spikes affect frontend reliability

Workflow

  1. Classify cacheability by asset and response type.
  2. Define TTL, revalidation, and purge strategy.
  3. Configure origin shielding and geo failover behavior.
  4. Apply signed URLs/cookies and edge access controls where needed.
  5. Monitor hit ratio, origin offload, and stale-content incidents.

Required Checks

  • Cache invalidation strategy supports safe releases
  • Sensitive content is never cached in public paths
  • CDN outage fallback path is documented and tested

Decision Framework

  • Prefer explicit contracts and compatibility rules before implementation.
  • If dependency risk is high, require timeout, retry, and fallback strategy per call path.
  • If async messaging is used, require idempotency, replay, and dead-letter handling.
  • If traffic patterns are volatile, require load, failover, and scaling validation before ship.

Common Rationalizations And Rebuttals

  • "Retries will handle failures automatically." -> Unbounded retries can amplify outages; use budgets.
  • "We can skip runbooks for now." -> Operational ambiguity delays incident recovery.
  • "Contract changes are minor." -> Small breaking changes cause broad downstream regressions.

Evidence Pack

  • Contract compatibility note and migration strategy (if applicable)
  • Failure-mode test evidence for dependency degradation and recovery
  • Observability snapshot (latency, error, saturation, or queue health)
  • Rollout and rollback steps with clear trigger thresholds

Exit Criteria

  • CDN improves performance without stale or unauthorized content risks
  • Edge delivery is measurable and operable