Hacker News new | ask | show | jobs
by 0xy 2195 days ago
Maintaining infinite platform/device compatibility, optimising video delivery, reducing bandwidth costs and new features to push the medium forward (like the choose-your-own-adventure thing they made).

Video delivery is hard. If you spend a month working on a basic Netflix clone showing a single clip it won't be 1/100th the performance of Netflix even if you use a CDN.

Netflix has optimizations for individual ISPs by placing content servers directly in their DCs.

Also, large organizations accumulate constant tech debt that need to be paid down. Features aren't infinitely scalable.

1 comments

The fact that they have people optimizing that obsessively is an indication of how little real work there is to be done. The thing plays videos, its played videos for years upon years, and all that's left in engineering terms seems to be to make it faster to a small degree that no user is likely to even detect.
It's not just playing video. Actually playing the video is easy. Delivering it to the end user is enormously challenging.

Even with a top-shelf CDN, you will have a non-negligible amount of customers having playback issues because of routing issues, peering disputes, congestion etc.

If delivery was easy, Akamai would not be a multi-billion dollar company. Microsoft wouldn't pay them millions, they'd just spin up some content servers themselves.

Saving X kb per 30 minutes of video streamed is "obsessively" optimizing something if you're serving a single video. If you're over 10% of all of Internet traffic, that can be millions of dollars saved a year, which pays for more than a few engineers even at SV salaries.
Couldn’t you argue that their obsessive optimization is one of the things that led them to dominate in the streaming space?
As a user I certainly appreciate it, but I think the actual content being delivered plays a much larger role than how many milliseconds its delivered in.