[194020] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Multi-CDN Strategies

daemon@ATHENA.MIT.EDU (Chris Woodfield)
Fri Mar 10 17:19:49 2017

X-Original-To: nanog@nanog.org
From: Chris Woodfield <rekoil@semihuman.com>
In-Reply-To: <CAC1-dtkK-MG6Tx8OTQf-izR+j5E2jUsLi4jbbRSt5vpn36WEqw@mail.gmail.com>
Date: Fri, 10 Mar 2017 14:19:44 -0800
To: Chris Grundemann <cgrundemann@gmail.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org

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 global regions. I=E2=80=99ve had decent =
experience with Dyn here, but Route53 has all the features you=E2=80=99d =
want as well. If possible, write tooling towards your DNS provider=E2=80=99=
s API to automate your failovers.

- Weight your distribution such that you never have one CDN turned off =
completely; you=E2=80=99ll want a small trickle of user traffic hitting =
every CDN so that the caches won=E2=80=99t be cold when you switch over =
to it.

- Make sure you have a distributed metrics service (ThousandEyes, =
WebMetrics, et al) testing your CDNs individually as well as the =
external hostname.

- Stay away from HTML- or Header-munging features when possible; stick =
with feature sets that are common (and implementable in similar ways) =
across your providers. (Similar advice goes for multi-vendor *anything*, =
TBH)

I could keep going, but if so, I might as well stick them into a =
powerpoint and submit a talk for Bellevue :)

-C

> On Mar 10, 2017, at 9:25 AM, Chris Grundemann <cgrundemann@gmail.com> =
wrote:
>=20
> Hail NANOG;
>=20
> Is anyone here leveraging multiple CDN providers for resiliency and =
have
> best practices or other advice they'd be willing to share?
>=20
> Thanks,
> ~Chris
>=20
> --=20
> @ChrisGrundemann
> http://chrisgrundemann.com


home help back first fref pref prev next nref lref last post