←back to thread

492 points storf45 | 1 comments | | HN request time: 0.001s | source
Show context
freditup ◴[] No.42154036[source]
I wonder if there will be any long term reputational repercussions for Netflix because of this. Amongst SWEs, Netflix is known for hiring the best people and their streaming service normally seems very solid. Other streaming services have definitely caught up a bit and are much more reliable then in the early days, but my impression still has always been that Netflix is a step above the rest technically.

This sure doesn't help with that impression, and it hasn't just been a momentary glitch but hours of instability. And the Netflix status page saying "Netflix is up! We are not currently experiencing an interruption to our streaming service." doesn't help either...

replies(27): >>42154059 #>>42154082 #>>42154106 #>>42154115 #>>42154122 #>>42154127 #>>42154144 #>>42154158 #>>42154174 #>>42154237 #>>42154240 #>>42154262 #>>42154269 #>>42154313 #>>42154369 #>>42154377 #>>42154390 #>>42154537 #>>42154579 #>>42154690 #>>42154772 #>>42154800 #>>42154855 #>>42154957 #>>42155322 #>>42155792 #>>42155880 #
ocdtrekkie ◴[] No.42154059[source]
So the issue is that Netflix gets its performance from colocating caches of movies in ISP datacenters, and a live broadcast doesn't work with that. It's not just about the sheer numbers of viewers, it's that a live model totally undermines their entire infrastructure advantage.

See: https://openconnect.netflix.com/en/

replies(9): >>42154072 #>>42154074 #>>42154076 #>>42154079 #>>42154138 #>>42154193 #>>42154199 #>>42154343 #>>42161993 #
1. _dark_matter_ ◴[] No.42154199[source]
I don't think that live doesn't work with caches. No one watching live would care about a O(s) delay, which is highly amenable to caching at ISPs and streaming changes from there to downstream clients. Offhand I'd say that would support O(ms) delay but no less.