News for hackers. Stuff that matters.
Re:Netflix, Long an AWS Customer, Tests Waters on Google Cloud by hinkley on Tuesday April 17, 2018 @12:48PM (#16860024)
How big doesn’t netflix have to get before it’s in their best interests to build data centers of their own?

Toolchains are maturing. They’ve figured out ways to get multiple uses from the same hardware. They shouldn’t be beholden to the rollout or geographical plans of two cloud providers.

I don’t even mean build out their entire infrastructure. I think even running your base load on your own hardware makes you understand your cloud situation much more profoundly.

Re:Netflix, Long an AWS Customer, Tests Waters on Google Cloud by theptip on Tuesday April 17, 2018 @02:15PM (#16860883)
They _had_ their own datacenters, and decided to move their control plane to the cloud (AWS) to avoid having to run the those datacenters themselves.

https://media.netflix.com/en/company-blog/completing-the-net...

This was a big deal in 2008 :)

(Maybe there's an even bigger size where it no longer makes sense for them to outsource this, but bidding GCP and AWS against each other seems like a reasonable strategy for their use-case).

Re:Netflix, Long an AWS Customer, Tests Waters on Google Cloud by treis on Tuesday April 17, 2018 @12:55PM (#16860077)
They have data centers of their own and distribute all of their own content. AWS powers the UI requests and their back office number crunching stuff. Everything after you push play is done via Netflix's own hardware.
Re:Netflix, Long an AWS Customer, Tests Waters on Google Cloud by martimarkov on Tuesday April 17, 2018 @01:27PM (#16860389)
Any links so I can read more on the subject? I’d love to get my hands on some material describing their infrastructure.
Re:Netflix, Long an AWS Customer, Tests Waters on Google Cloud by treis on Tuesday April 17, 2018 @01:30PM (#16860425)
Re:Netflix, Long an AWS Customer, Tests Waters on Google Cloud by hinkley on Tuesday April 17, 2018 @03:29PM (#16861516)
That seems to be more about their edge caches, which is interesting [and partly answers one of bad assumptions] but not the same.