News for hackers. Stuff that matters.
Re:Verizon's accidental mea culpa by ctdonath on Thursday July 17, 2014 @03:46PM (#8049762)
From elsewhere on HN:

All of Netflix, in HD, on 24TB.

Netflix could solve the bandwidth problem by just mailing the whole library to customers. "Never underestimate the bandwidth of a station wagon full of magnetic tapes."

Re:Verizon's accidental mea culpa by grecy on Thursday July 17, 2014 @04:08PM (#8049889)
Netflix offer this as an option to any ISP that wants it, free.

They will put a server in a data center anywhere an ISP wants, and they'll manage the whole syncing thing so the ISP doesn't even know it's there. After that, all content comes from that cache.

Re:Verizon's accidental mea culpa by mb0 on Thursday July 17, 2014 @04:20PM (#8049952)
To clarify Grecy's statement, netflix offers openconnect[1] for to ISPs as a caching mechanism, and the box contains about 108TB of disk capacity[2]. The boxes are sent to ISPs instead of customers though.

[1] https://www.netflix.com/openconnect

[2] https://www.netflix.com/openconnect/hardware

Re:Verizon's accidental mea culpa by gnarbarian on Thursday July 17, 2014 @04:24PM (#8049986)
While the "oil tanker full of hard drives" approach has incredible bandwidth the latency is a bit of a problem. Especially when the Netflix library is updated constantly.

My personal opinion is that you should cache/co-locate your data close the the edge of the edge of your network whenever it presents a benefit for congestion and price.

Re:Verizon's accidental mea culpa by opendais on Thursday July 17, 2014 @05:46PM (#8050385)
Yep. Of course when Verizon blocks you from doing that...