Origin Shield

Origin shield is an extra caching tier placed between a CDN's edge locations and your origin server. When an edge misses, it asks the shield location instead of the origin. Only the shield contacts the origin, and it caches the result for all edges.

Why it matters

Without a shield, a popular file expiring at the same time can trigger a miss at dozens of edge locations, each hitting your origin separately. The shield collapses these into one request. This raises the overall cache hit ratio, reduces origin load and egress cost, and protects fragile origins during spikes or after a purge. The trade-off is one more hop on a miss, adding a little latency for the first request.

CDN vendors name it differently: Amazon CloudFront calls it Origin Shield, Fastly calls it shielding, and Cloudflare provides tiered caching.

Example

Without shield: 40 edges miss -> 40 origin requests
With shield:    40 edges miss -> 1 shield request -> 1 origin request

Choose a shield region close to your origin to keep that leg short.

Common mistakes

• Enabling it for a tiny site where the origin load is already low.
• Placing the shield far from the origin.
• Expecting it to speed up uncacheable dynamic responses.
• Forgetting that purges may need to reach the shield as well.

Related

• CDN
• Cache hit ratio
• Reverse proxy
• Edge computing

यह पेज सामान्य जानकारी है, जिसे हमारी संपादकीय टीम ने लिखा है और दस्तावेज़ीकरण बदलने पर अपडेट किया जाता है। सर्वर और प्रदाता अलग-अलग होते हैं, इसलिए बदलाव पहले सुरक्षित तरीके से जाँचें। देखें: संपादकीय नीति और अस्वीकरण.