Origin Offload with Origin Shielding

Just by using the CacheFly CDN, you get faster delivery to end users around the globe, reduction in capacity needed at your origin, as well as reduced egress from your origin. As POPs around the globe cache and deliver the content, often with 99+ % cache hit ratio, your origin is greatly offloaded.

For cacheable content, multiple concurrent requests at a POP are collapsed, allowing thousands of end users CDN requests to collapse down to one or a few requests from each POP location to your origin.

And Origin Shielding kicks that up a notch and takes that even a step further....

Origin Shielding:

• Reducing Origin Egress

• Reducing Origin Capacity Required

• Providing Faster End User Delivery

As requests come in around the globe - rather than each POP or regional POP reaching out to origin directly - the POPs will reach out instead to any Origin Shared Shield POP configured. Usually we recommend for configuration, to select a shared shield location closest to your origin.

If content is already cached at the shield, it is delivered to end users, cached at regional POPs for subsequent requests, and no additional origin requests were made. If the Shield POP does not yet have the content cached, the shield POP will make the request to the origin, and cache at the shield for subsequent requests.

This can greatly offload origin egress and capacity needed at your origin. Some origins such as AWS S3 or other external origins may charge hefty fees for egress out or even request fees.

Speed of end user delivery is also a feature of Origin Shielding, as content is delivered more quickly from Cache, rather than needing to request and wait for content from the Origin.