4 ms·
The sad thing is they're having issues with loading login pages, authenticating via API, app API backend routes... pretty much every layer of their app stack an
by geerlingguy 7y ago
The sad thing is they're having issues with loading login pages, authenticating via API, app API backend routes... pretty much every layer of their app stack and that's _before_ any video can be streamed to end users.
I hoped they would've had the first few layers pretty scalable and load tested, but either they had orders of magnitude more load than they ever planned for, or they didn't actually load test to millions of users (more likely IMO).
- buckminster 7y agoIt makes some sense if it's the user onboarding that's failing. That's the one part that should see much less traffic in normal operation.
- awill 7y agoThat's actually the hard part. Video streaming is easy, and done with CDNs.
- Slartie 7y agoSure, handing over giant checks to Akamai is easy, but it becomes a lot harder if you do the CDN part yourself. Like all the really big streaming video providers do, because otherwise they wouldn't be competitive at scale.
- Mindwipe 7y agoWell, it's not "easy", at Netflix scale. Lots of Netflix traffic is done via local caching servers at ISPs as CDN delivery isn't reliable enough. Minimising playback latency is really, really hard and NF do very well here. Robust geofiltering in those scenarios is hard if you're trying to check the video essence and not just the license. Having said that, there are a lot of reasonably mature solutions in the market to address many of these points, and it doesn't appear that was the issue yesterday.
- durden0 7y agoThis makes more sense to me then all the talk about CDN's. CDN's don't solve all problems.