Re:Working at Netflix 2017
by phamilton on Tuesday May 16, 2017 @05:17PM
(#14353372)
Supplying sufficient video to be responsible for 25% of consumer internet bandwidth is a different story.
[ Parent
| on HN ]
Re:Working at Netflix 2017
by toomuchtodo on Tuesday May 16, 2017 @05:30PM
(#14353471)
Can you be more specific? Do you mean producing their original content? Or rendering renditions for each bitrate, and then pushing those renditions out to their custom CDN appliances? (OpenConnect)
I can most definitely get behind original content production being hard. But pushing a couple hundred TB (or even low double digit PB) of data out to CDNs doesn't require a fleet of devs.
Total content is likely closer to 100 PB. The "25% of consumer bandwidth" is a proxy for how heavily Netflix is used.
Take a look at some of their open source projects and their tech blog to get a feel for the problems they solve at their scale.
https://netflix.github.io/ https://medium.com/netflix-techblog
Some things I find personally interesting:
They run a 5000 node Cassandra cluster.
They can failover an entire datacenter in 27 minutes.
Re:Working at Netflix 2017
by user5994461 on Tuesday May 16, 2017 @05:46PM
(#14353592)
Akamai can do that for you just fine.
Apparently, Akamai does about 30 Terabits/s[0]. Netflix does "tens of terabits per second"[1].
Essentially, Netflix is about as big as Akamai when it comes to content delivery.
[0] https://www.akamai.com/us/en/about/facts-figures.jsp
[1] https://media.netflix.com/en/company-blog/how-netflix-works-...