2nd January, 2019
3 Min read
Book a Demo
Multi-CDN is a strategy of using more than one CDN provider in order to further improve latency, uptimes and cost efficiency on a global scale.Recently we have received many questions from our customers about the multi-CDN technology, so we’ve decided to write this quick overview to clarify how multi-CDNs work, and how you can easily employ a multi-CDN solution in your company.
When adopting a Multi-CDN Strategy, the choice is between managing it via Advanced DNS alone (plus n CDN Endpoints) or based on some intelligent HTTP Engine on top of the DNS Layer. Both approaches have their pros and cons but the need for Advanced DNS Management is obvious and pays itself even easily.
There are two main scenarios here: either you need Multiple CDNs, each catering to specific Geographies, and/or they are load balanced with each other everywhere.
The CNAME Records in question will thus point to some load balanced intermediate Hostnames (instead of straight to your only CDN) in the back end, and these in turn will point to a specific (CDN) Hostname depending – among the “simplest” possible logics – on the End Users’ geographic location (first case above); whether you will see the intermediate load balanced Hostname when running a dig/nslookup command, depends on the Product/Technology and we cater for both scenarios.
Advanced DNS Products are required to manage Multi-CDN Delivery Strategies; in general, they’re made up of three Components:
Another, even more sophisticated approach to Multi-CDN is via DNS based on HTTP Intelligence.
Intelligent HTTP Engines like these analyze Web Traffic Performance Key Metrics through their own crowd-sourced Platform’s benchmarks – or even metrics provided by the Customers – and offer Application Load Balancing by taking decisions based on these metrics.
This approach leads to even more efficient Load Balancing and higher Availability and ensures that every End User, in any geography, at any time, is always served the most performant CDN out of the available pool.
Of course there are, and we’ve seen a number of these over the years; these are to be seen as complementary and not as exclusive (you can factor in more than just one logic). Think about the following use cases:
This is by no means an exhaustive list of scenarios, but rather more of a way to pick your mind around typical use cases we’ve come across over the years.
If you have any questions about how we can help you choose and implement a multi-CDN, contact us today to help you out with your performance and security needs.
Schedule a call with our experts. Discover new technology and get recommendations to improve your performance.