vladbri brilliant barney

[Orestes Hardy]

I pulled this chapter together from dozens of sources that were at times somewhat contradictory. Facts on the ground change over time and depend who is telling the story and what audience they're addressing. I tried to create as coherent a narrative as I could. If there are any errors I'd be more than happy to fix them. Keep in mind this article is not a technical deep dive. It's a big picture type article. For example, I don't mention the word microservice even once :-)

Given our discussion in the What is Cloud Computing? chapter, you might expect Netflix to serve video using AWS. Press play in a Netflix application and video stored in S3 would be streamed from S3, over the internet, directly to your device.

Another relevant factoid is Netflix is subscription based. Members pay Netflix monthly and can cancel at any time. When you press play to chill on Netflix, it had better work. Unhappy members unsubscribe.

The client is the user interface on any device used to browse and play Netflix videos. It could be an app on your iPhone, a website on your desktop computer, or even an app on your Smart TV. Netflix controls each and every client for each and every device.

Everything that happens before you hit play happens in the backend, which runs in AWS. That includes things like preparing all new incoming video and handling requests from all apps, websites, TVs, and other devices.

In 2007 Netflix introduced their streaming video-on-demand service that allowed subscribers to stream television series and films via the Netflix website on personal computers, or the Netflix software on a variety of supported platforms, including smartphones and tablets, digital media players, video game consoles, and smart TVs.

Netflix succeeded. Netflix certainly executed well, but they were late to the game, and that helped them. By 2007 the internet was fast enough and cheap enough to support streaming video services. That was never the case before. The addition of fast, low-cost mobile bandwidth and the introduction of powerful mobile devices like smart phones and tablets, has made it easier and cheaper for anyone to stream video at any time from anywhere. Timing is everything.

Building out a datacenter is a lot of work. Ordering equipment takes a long time. Installing and getting all the equipment working takes a long time. And as soon they got everything working they would run out of capacity, and the whole process had to start over again.

The long lead times for equipment forced Netflix to adopt what is known as a vertical scaling strategy. Netflix made big programs that ran on big computers. This approach is called building a monolith. One program did everything.

What Netflix was good at was delivering video to their members. Netflix would rather concentrate on getting better at delivering video rather than getting better at building datacenters. Building datacenters was not a competitive advantage for Netflix, delivering video is.

It took more than eight years for Netflix to complete the process of moving from their own datacenters to AWS. During that period Netflix grew its number of streaming customers eightfold. Netflix now runs on several hundred thousand EC2 instances.

The advantage of having three regions is that any one region can fail, and the other regions will step in handle all the members in the failed region. When a region fails, Netflix calls this evacuating a region.

The header image is meant to intrigue you, to draw you into selecting a video. The idea is the more compelling the header image, the more likely you are to watch a video. And the more videos you watch, the less likely you are to unsubscribe from Netflix.

The first thing Netflix does is spend a lot of time validating the video. It looks for digital artifacts, color changes, or missing frames that may have been caused by previous transcoding attempts or data transmission problems.

A pipeline is simply a series of steps data is put through to make it ready for use, much like an assembly line in a factory. More than 70 different pieces of software have a hand in creating every video.

The idea behind a CDN is simple: put video as close as possible to users by spreading computers throughout the world. When a user wants to watch a video, find the nearest computer with the video on it and stream to the device from there.

In 2007, when Netflix debuted its new streaming service, it had 36 million members in 50 countries, watching more than a billion hours of video each month, streaming multiple terabits of content per second.

At the same time, Netflix was also devoting a lot of effort into all the AWS services we talked about earlier. Netflix calls the services in AWS its control plane. Control plane is a telecommunications term identifying the part of the system that controls everything else. In your body, your brain is the control plane; it controls everything else.

In 2011, Netflix realized at its scale it needed a dedicated CDN solution to maximize network efficiency. Video distribution is a core competency for Netflix and could be a huge competitive advantage.

The number of OCAs on a site depends on how reliable Netflix wants the site to be, the amount of Netflix traffic (bandwidth) that is delivered from that site, and the percentage of traffic a site allows to be streamed.

Within a location, a popular video like House of Cards is copied to many different OCAs. The more popular a video, the more servers it will be copied to. Why? If there was only one copy of a very popular video, streaming the video to members would overwhelm the server. As they say, many hands make light work.

Right now, up to 100% of Netflix content is being served from within ISP networks. This reduces costs by relieving internet congestion for ISPs. At the same time, Netflix members experience a high-quality viewing experience. And network performance improves for everyone.

What may not be immediately obvious is that the OCAs are independent of each other. OCAs act as self-sufficient video-serving archipelagos. Members streaming from one OCA are not affected when other OCAs fail.

I'm not entirely sure if Stack Overflow is the correct website to ask this question, but I have been thinking about it ever since a friend mentioned it to me a week ago. I know on a baseline level what hardware acceleration does: offloads certain workloads to other components in your computer (i.e. your GPU or sound card) to improve performance in various applications. I just would like to know what exactly is happening when hardware acceleration is on v/s off when streaming a Google Chrome window and why it makes a difference in a completely different application.

If you're unfamiliar with what I'm referencing in the title, here's a simple example of what I mean: Let's say you want to watch a Netflix show or sporting event with your friends on Discord, so you all hop in a call together on the app to watch you stream the video in a Chrome tab. However, when your friends join the stream, they can hear the audio of what you're streaming but the video feed is blacked out for those watching. Interestingly enough, one of the solutions people have found to this issue is disabling hardware acceleration in Google Chrome's settings which allows the video and audio to be streamed no problem.

It makes sense why this occurs: to prevent potential piracy and illegal redistribution of copywrited material, but why does disabling hardware acceleration re-enable this functionality? Does hardware acceleration allow data to be shared between apps? Does Discord set a flag saying a particular window/screen is being streamed and Chrome can only "see" that flag while hardware acceleration is enabled?

I guess the underlying question is: how does having hardware acceleration enabled allow Netflix, a TV provider or any other website for that matter to know their content is being streamed?

The hardware acceleration allows the HDCP content to remain encrypted all the way to the display. By disabling it, the video is decrypted in software usually at a reduced resolution and/or frame rate.

Offer subject to change. Receive Netflix Standard with ads while you maintain 1 qualifying Go5G Next, Go5G Plus or Magenta Max line or 2+ Go5G or Magenta lines in good standing. Netflix account, plan availability & compatible device required. Alternative discount toward different Netflix streaming plans may apply. Not redeemable or refundable for cash; cannot be exchanged for Netflix gift subscriptions. Cancel Netflix anytime. Netflix Terms of Use apply: www.netflix.com/termsofuse. 1 offer per T-Mobile account; for existing Netflix members it may take 1-2 bill cycles during which time you will continue to be charged separately for any existing Netflix account. If you link an existing Netflix account to this offer, terminating the qualifying line(s) will not automatically cancel your Netflix membership, and Netflix will automatically resume charging your existing payment method that they have on file. Like all plans, features may change or be discontinued at any time; see T-Mobile Terms and Conditions at T-Mobile.com for details.

Offer subject to change. Receive Netflix Standard with ads while you maintain a qualifying line in good standing. Netflix account, plan availability & compatible device required. Alternative discount toward different Netflix streaming plans may apply. Not redeemable or refundable for cash; cannot be exchanged for Netflix gift subscriptions. Cancel Netflix anytime. Netflix Terms of Use apply: www.netflix.com/termsofuse. 1 offer per T-Mobile account; for existing Netflix members it may take 1-2 bill cycles during which time you will continue to be charged separately for any existing Netflix account. If you link an existing Netflix account to this offer, terminating the qualifying line will not automatically cancel your Netflix membership, and Netflix will automatically resume charging your existing payment method that they have on file. Like all plans, features may change or be discontinued at any time; see T-Mobile Terms and Conditions at T-Mobile.com for details.

90f70e40cf