Leveraging the garden variety content delivery network (CDN) is quickly becoming a popular model for serving up your online content. CDNs are fast, resilient, cost-effective and allow you to sleep at night knowing your content is in good hands.
However, based on where you are, what you’re doing and more importantly, where your CDN ends up sending you for your content, its performance will fluctuate – sometimes very sharply, possibly to the point of failure, and for periods longer than your users will forgive.
If this happens, your boss or your wallet will likely be equally unforgiving. That’s why leveraging multiple CDNs is a solid mitigation tactic. But you may make that connection because you’re smart and see a competitive advantage. But think about those performance fluctuations. To which CDN do you send your users to optimize performance for every end user at any point in time?
Dyn’s Real Time Traffic Management (RTTM) feature is standard with our Advanced Traffic Manager feature in DynECT Managed DNS. RTTM allows you to establish address pools in any of seven distinct geographic regions across the world, directing traffic to the best-performing endpoint in each pool.
As each CDN provides you the locations from where your content is delivered, you plug them into RTTM address pools with at least one endpoint per pool for each CDN you use. We monitor each endpoint using a protocol and interval you specify and automatically direct traffic to the currently best-performing CDN.
All of this is fully configurable through the DynECT management portal and via our API.
Employing a multiple CDN model to serve your content isn’t for everyone out there right now. But if you see it in your future, do it right the first time and maximize your performance, resiliency and agility by implementing DynECT Managed DNS alongside it.