Per-Entity Metadata Working Group

["Cantor, Scott" <>]

On 9/14/16, 3:16 PM, 
"
 on behalf of Nick Roy" 
<
 on behalf of 
>
 wrote:

>    That is exactly why having at least one CDN, and preferably more than 
>    one, is relevant to a failover strategy.  Geographic and logical 
>    redundancy.  Publishing to more than one CDN than one means you can 
>    configure clients to fail over between more than one service.  Keeping 
>    the naming separate and putting the failover between CDNs in the client 
>    lets clients specify parameters they are comfortable with for things 
>    like latency.

But server-side lets you mitigate the cost of timeouts so that every client 
doesn't have to wait an unpredictable amount of time before realizing 
something isn't working.

You really can't realistically have much more than maybe 2 sources before the 
timeouts start to get too long in sequence. Or you have to set really, really 
low timeouts and hope things keep up.

Using parallel retrieval to mitigate the overlap is, IMHO, a bit too much to 
expect.

-- Scott