Warpcache Multi-CDN Explained
1. Collecting data from RUM
After the webpage has loaded, we perform some performance tests in the background and without interfering with the users’ experience. This form of data collection is called Real User Measurements or RUM in short.
2. ANALYSING THE RESULTS
After receiving the anonymised performance data, it will be analysed and made available for the intelligent DNS server.
3. INTELLIGENT DNS RESPONSES
When a DNS request comes in, we’ll look into the data that was collected and determine the best CDN provider for that particular request. What is best is determined by multiple factors including but not limited to ISP, location, availability of the CDN, and the performance profile for the hostname that’s being requested.
What you get
No single CDN is fastest all over the world. Warpcache transparently combines the strongest points of multiple CDNs into one big CDN. The full network can be controlled through our easy-to-use web interface or super simple API. You can easily create and modify properties as well as purge objects from all CDNs at the same time.
If you have mainly large files you wish to serve, we recommend you optimise the CDN selection based on throughput.
In a multiple second download action, a few milliseconds extra to establish the initial connection won’t matter much for the total time it takes to transfer the whole file. What does matter is the available capacity at the various CDNs to send the file at the highest possible speed, ideally only limited by the maximum bandwidth available to the enduser.
If you mainly wish to serve smaller files, we recommend you optimise the CDN selection for an optimal RTT (Round Trip Time).
If the total transfer time is in the milliseconds, every additional millisecond has a big impact on the total transfer time. When optimising for latency, we’ll automatically select the CDN that is fastest from the location of your end user at the time of the request.
We run these automated measurements real time and non-stop – Warpcache never sleeps!
Every system eventually fails and so do CDNs.
Often those failures are not global but regional. The cause could be internal to the CDN provider like maintenance or capacity problems, or external where CDNs are blocked by countries or due to disputes over peering agreements.
Our platform detects those issues and will reroute traffic to the other CDNs that are available and performing well, decreasing the risk of downtime for your business.