Anand Vijayan, Senior Product Manager
Rachel Thornton, Senior Software Engineer
Media CDN is Google Cloud's content delivery network for large-scale workloads, including video streaming and software downloads, leveraging Google's global network to provide high-performance delivery.
Origin shielding is a critical content delivery mechanism that protects your origin servers from being overwhelmed by cache-fill requests. Without it, multiple edge caches can simultaneously request the same content, leading to a 'thundering herd' problem that significantly increases origin load and egress costs.
Media CDN delivers robust origin shielding by default, a feature that sets it apart from other CDNs. It strategically deploys "long-tail caches" within Google's network, which serve as an intermediate layer. These caches consolidate requests from numerous downstream caches, sending a single, unified request to your origin. This includes a default behavior called "request collapsing," where multiple user-driven cache fill requests for the same cache key are actively combined into one origin request per edge node. This significantly reduces the direct load on your origin server and minimizes egress bandwidth needs.
Introducing flexible origin shielding (preview): While Media CDN's default origin shielding is highly effective, flexible origin shielding introduces a new level of control and flexibility. This advanced feature empowers you to explicitly configure specific shield locations closer to your origin as opposed to where end users are located. This means you can direct aggregated cache-fill traffic through a single designated shield region, regardless of where the initial user request originated. By choosing an optimal shield location, you can further:
This granular control over shield locations makes flexible origin shielding particularly beneficial for customers with centralized origins, allowing for a more tailored and efficient content delivery strategy.
Flexible origin shielding (Public Preview) is initially available in me-central1(Doha) and africa-south1 (Johannesburg).
Let’s consider an example for media content with a centralized origin, like one located in Doha, Qatar, serving a globally distributed audience, Media CDN's default origin shielding, while robust, can sometimes lead to suboptimal routing and increased latency for certain architectures. This is because the default shielding operates based on the end-user's location, not necessarily the origin's, and may route requests through long-tail caches (LTCs) that are geographically distant from the Doha origin.
With flexible origin shielding, you gain precise control to address this challenge, by optimizing it for your architecture. You can now explicitly select a specific Long-Tail Cache (LTC) region, such as Doha, to serve as your primary origin shield. This means that nearly all cache-fill traffic from your globally distributed users will be intelligently routed across the Google backbone and consolidated through the designated Doha LTC before reaching your origin server.
This configuration offers several significant benefits:
To get started with flexible origin shielding, follow the steps in our flexible shielding documentation .