←back to thread

208 points henrijn | 1 comments | | HN request time: 0s | source
Show context
ksenzee ◴[] No.42160131[source]
The infrastructure has been rock-solid. I’ve never seen a service grow this fast without any noticeable outages. The architecture and execution are obviously informed by serious experience at Twitter, but it’s also clear that management is giving them everything they need to do the job right.
replies(4): >>42160170 #>>42160324 #>>42160542 #>>42163517 #
nicce ◴[] No.42160324[source]
> The infrastructure has been rock-solid. I’ve never seen a service grow this fast without any noticeable outages. The architecture and execution are obviously informed by serious experience at Twitter, but it’s also clear that management is giving them everything they need to do the job right.

The world has changed quite bit. If you have deep pockets and you can use AWS etc., it isn't a major problem anymore. However, if they indeed run it on their own data centers, that is impressive.

replies(4): >>42160426 #>>42160457 #>>42160493 #>>42161085 #
xboxnolifes ◴[] No.42160457[source]
I'm not so sure about this when not even 24 hours ago Netflix has streaming issues running on AWS infrastructure, and existing social media sites still have outages.
replies(2): >>42160934 #>>42181090 #
1. nicce ◴[] No.42160934[source]
> Netflix has streaming issues running on AWS infrastructure

I think the performance of Netflix is highly dependent of ISP's data centers [1].

But yeah, there are still limits where the cloud won't help you.

If you whole infrastructure is designed to serve "historical" content instead of streaming, some bottlenecks cannot be avoided if you want to server low-latency sports stream. This came by surprise for me, but apparently betting has still significant role for the viewers.

[1]: https://openconnect.netflix.com/en/