Technology Encyclopedia Home >How is CDN back-to-origin traffic generated?

How is CDN back-to-origin traffic generated?

Created on 2025-04-22 11:15:55
57

CDN back-to-origin traffic is generated when a requested resource is not found in the edge servers of a Content Delivery Network (CDN). This can occur for several reasons, such as the resource being outdated, the edge server not having a cached version, or the resource being accessed for the first time. When this happens, the CDN edge server sends a request to the origin server (the original server hosting the content) to retrieve the resource.

Explanation:

  1. Cache Miss: When a user requests a resource, the CDN checks its edge servers for a cached version.
  2. Resource Not Found: If the resource is not found in the cache (a cache miss), the CDN edge server sends a request to the origin server.
  3. Origin Retrieval: The origin server responds with the requested resource, which is then cached at the edge server for future requests.

Example:
Imagine a user in New York requests a video from a website. The CDN checks its edge server in New York, but the video is not cached there. The CDN edge server then sends a request to the origin server in Los Angeles to retrieve the video. Once retrieved, the video is cached in New York for faster delivery to subsequent requests from users in that region.

Recommendation for Cloud Services:
For efficient management of CDN traffic and back-to-origin requests, consider using services like Tencent Cloud's Content Delivery Network (CDN). Tencent Cloud CDN offers global coverage, high-speed delivery, and intelligent caching strategies to minimize back-to-origin traffic and improve user experience.