[194082] in North American Network Operators' Group
Re: Multi-CDN Strategies
daemon@ATHENA.MIT.EDU (Danijel Starman)
Wed Mar 15 05:54:12 2017
X-Original-To: nanog@nanog.org
In-Reply-To: <112EB79C-9BF4-4D95-B303-21081472926B@semihuman.com>
From: Danijel Starman <theghost101@gmail.com>
Date: Wed, 15 Mar 2017 10:53:49 +0100
To: Chris Woodfield <rekoil@semihuman.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
On Fri, Mar 10, 2017 at 11:19 PM, Chris Woodfield <rekoil@semihuman.com>
wrote:
> I have some experience with this; a few things off the top of my head:
>
> - It=E2=80=99s usually best to leverage some sort of =E2=80=9Csmart=E2=80=
=9D DNS to handle CNAME
> distribution, giving you the ability to weight your CNAME distribution vs=
.
> only using one CDN all the time, or prefer different CDNs in various glob=
al
> regions. I=E2=80=99ve had decent experience with Dyn here, but Route53 ha=
s all the
> features you=E2=80=99d want as well. If possible, write tooling towards y=
our DNS
> provider=E2=80=99s API to automate your failovers.
>
I've seen people do this in their code too, send approximate percentages of
requests to different providers but then you need to do a code push for
failover.
