Re:Google Caching Overview
by codewithcheese on Sunday August 30, 2015 @10:17AM
(#10143369)
Does Netflix have caching beyond AWS data centers?
Yes:
https://openconnect.netflix.com/peeringLocations/
This was somewhat famously part of the network neutrality debate because certain large ISPs were trying to claim that their customers were transferring too much from Netflix and thus needed to be double-billed but those same ISPs refused to install the free OpenConnect servers which would have reduced that traffic.
My understanding though is that if you have an open connect box on your network it can act as a DDOS, stressing all your infrastructure closer to the customers. Netflix eats all bandwidth.
That's not a DDOS – it's called “actually delivering the service your customers paid for”. If you've underprovisioned your network, that might be a problem but it's not an attack.
It's also something of a best-case scenario because the only party affected is the same party which has the ability to fix the problem: since it's on your network, you can add additional capacity or institute some sort of fair-queuing without the need to negotiate with outside companies.
Re:Google Caching Overview
by chinathrow on Tuesday September 01, 2015 @05:16AM
(#10151409)
I imagine the Open Connect box would do automatic bitrate tuning for all users on that network for immediate mitigation and notify obviously Netflix and the open connect ISP for long term capacity management.
Oh yeah https://openconnect.netflix.com/
I wonder, if local cache setups would have different impact on jurisdiction, taxes and such. Google is known to always say you deal with Ireland, e.g. outside of the US but what if the cache is local?