4 ms·
> "we could do this a lot faster and eventually worldwide if we hitch our wagon to this new AWS thing" Standard reminder, this was for all the non-content deli
by secabeen 4y ago
> "we could do this a lot faster and eventually worldwide if we hitch our wagon to this new AWS thing"
Standard reminder, this was for all the non-content delivery parts of Netflix. They have always and continue to run their own CDN in-house, and don't use AWS for that part. It also took almost 8 years to fully transition to AWS:
https://ayushhsinghh.medium.com/case-study-how-netflix-is-using-aws-and-its-own-cdn-64ca6282eda0 https://ayushhsinghh.medium.com/case-study-how-netflix-is-us...
- jedberg 4y agoThat article is full of inaccuracies FYI. It took six years, not eight, and 95% of the transition was done in four years. Also, Netflix didn't always have its own CDN. We used Level3, Limelight, and Akamai to deliver video from 2010 until about 2012/13. And content is still stored in AWS. It's all rendered there and all the original copies are stored there. You are correct though that Netflix never delivered video bits to users via AWS, because it was cost prohibitive.