Netflix case study


Netflix is one of the most popular linear TV experience apps in the world today, with millions of customers around the world. The application gives its users the ability to live stream videos and movies from its data bank on the basis of hassle-free subscriptions. With this new technological age, speed and ease of use are everything. Netflix moved from its own server centres to the cloud technology because it saw the growing potential of the niche, however it still uses micro servers to manage its video streaming facilities and has its own CDN called Open Connect. Netflix uses Amazon Web Services (AWS) for its hosting, and operates on the TCP protocol. Netflix has Message Security Layer that aims at protecting data transmission to and from the Netflix network, which is a protocol developed by Netflix itself. The company operates with Open Connect Appliances on the network. The whole network infrastructure aims at making the streaming of videos fast and secure for users and for the company itself.


Public loves content from the TV, nonetheless they don't adore the experience of linear TV, where networks present programs solely at specific times on screens that are non-portable with complex remote panels. Nowadays internet entertaining - which is based on demands, is custom-made, and accessible on any screen - is substituting linear TV. The biosphere's principal linear TV systems now propose their program design on request by means of apps that operate on smart TVs and mobile phones. These apps, like CBS All Access etc., allow binge watching and catch-up watching. Prevailing linear systems that propose persuasive internet apps will produce more viewership and become increasingly valued. Networks that flop to advance first-class apps misplace viewing and income. Netflix is not one of these typical linear TV networks. It is a global web-stimulation and entertainment services network offering motion pictures and TV arrangement business for free, with boundless review on any web associated screen for a moderate, no-responsibility month to month charge (Netflix Investors 2018). Netflix is an engaged enthusiasm brand, with a level charge boundless review business free plan of action.

Internet Service Provider (ISP) endorsers pay for web access and hope to have the capacity to appreciate web stimulation, for example, Netflix. Netflix's Open Connect program underpins several expansive and little ISPs to legitimately interconnect with the Netflix organize for nothing in local areas, as opposed to experiencing outsider travel suppliers, which brings down both our expenses and that of the ISPs. With Multichannel Video Programming Distributors (MVPDs) that have a web skilled TV set top gadget, for example, DISH, Virgin (UK), Liberty Global and Sky (crosswise over Europe) and numerous others, Netflix offers coordinated review encounters (and much of the time incorporated charging) which increment the utilization of the administrator set top gadget. While some MVPDs need to repress Netflix's development, most would incline toward that its development occurs through their remote control and set top understanding (Willemsen, 2016).

This paper aims at describing the networking architecture of this Internet giant. It discusses the architecture, layers, protocols, ISP requirements, related devices and applications, and other data relating to how Netflix operates as networking system.

  1. Architecture

Netflix uses what is called a “monolithic architecture”. Netflix truly introduced an insurgency around ten years back by modifying the applications that run the whole administration to fit into a microservices architecture — which implies that every application, or microservice's code and assets are its own one of a kind. It won't impart any of it to some other application essentially. Also, when two applications do need to converse with one another, they utilize an application programming interface (API) — a firmly controlled arrangement of guidelines that the two projects can deal with. Engineers would now be able to roll out numerous improvements, little or colossal, to every application as long as they guarantee that it plays well with the API. Also, since the one program knows different API appropriately, no change will break the trading of data.

Netflix gauges that it utilizes around 700 microservices to control every one of the numerous pieces of what makes up the whole Netflix administration: one microservice stores what all shows you watched, one deducts the month to month charge from user’s Visa, one furnishes user’s gadget with the right video documents that it can play, one investigates user’s watching history and utilizations calculations to figure a rundown of motion pictures that user’s will like, and one will give the names and pictures of these films to be appeared in a rundown on the fundamental menu. What's more, that is a glimpse of something larger. Netflix architects can make changes to any piece of the application and can present new changes quickly while guaranteeing that nothing else in the whole administration separates.

To operate these microservices, a huge system of PC servers is required, and Netflix once possessed one all alone, however they understood that the very fast pace that they developed at — and expected to keep doing so — was troublesome on the off chance that they invested their energy building PC frameworks that can bolster their product and continue fixing and adjusting them to meet their requirements. That is the point at which they chose to dispose of keeping up their very own servers and move the majority of their stuff to the cloud — i.e. run everything on the servers of another person who managed keeping up the equipment while Netflix engineers composed several projects and sent it on the servers quickly. The cloud-based foundation they decided for their organization was Amazon Web Services (AWS).

  1. Content Delivery Network (CDN)

For Netflix and other top-level websites, where a huge number of long periods of video content are handed-off over the web between their servers and every one of the clients, a lot bigger system of servers is expected to look after execution. They do this by structure something many refer to as a Content Delivery Network (CDN). Netflix prior utilized an assortment of CDN networks — operated by mammoths, for example, Akamai, Level 3 and Limelight Networks to convey their substance. Yet, a developing client base method they should convey higher number of substances at more areas while bringing down expenses. CDNs are intended to convey web-based substance to watchers by bringing it closer to where they're viewing. Netflix initially re-appropriated spilling video conveyance to outsider CDN providers, however as the organization developed, these sellers attempted to help the traffic. Netflix required more authority over the administration and client experience, and this drove them to fabricate their own CDN, called Open Connect.

In this perspective, rather than depending on AWS servers, Netflix introduced their own one of a kind CDN around the globe. However, it has one and only purpose — to store content astutely and convey it to clients. Netflix hits manages web access suppliers and gives them the red box you saw above at no expense. ISPs introduce these alongside their servers. These Open Connect boxes download the Netflix library for their area from the fundamental servers in the US — if there are various of them, each will rather store content that is increasingly prominent with Netflix clients in a district to organize speed.

  • Open Connect and ISPs

Utilized for its video streaming administrations, actually, Open Connect can be portrayed as a system of server farms far and wide: its motivation is to convey Netflix content nearer to its client. In this way, there are a huge number of Open Connect Appliances (OCAs) around the globe and they appropriate 100% of the video traffic. To sum things up, everything occurring on Netflix before hitting play is running on AWS cloud, at that point the OCAs dominate.

A pivotal part of Open Connect is the foundation of associations with the Internet Service Providers (ISPs): The Open Connect Appliances (OCAs) are interconnected with the ISPs. Undoubtedly, Open Connect was set up in 2011 for two reasons. First it turned out to be practically inescapable to work with ISPs in light of the fact that Netflix represented a developing extent of their exercises. At that point it was likewise an approach to help the developing action of the organization. It is very simple for ISPs to take part in an association, since Netflix provides numerous clarifications and a rule to tell the best way to send OCAs. It likewise records the diverse choices, the commitment procedure and the prerequisites.

The most ideal Netflix spilling transmission capacity, as indicated by Netflix, and the Internet speed that will be required for downloads is as per the following (Sclater 2013):

No less than 10 Mbps download speeds or higher at home are required for the system if clients need to video stream. Shockingly better is 20 Mbps or higher, yet then they're adding more expense to the month to month bill. Getting in the middle of 10 Mbps and 20 Mbps is presumably perfect.

Open Connect apparatuses store and convey content inside neighbourhood Internet Service Provider (ISP) server farms, which separates the Netflix administration from the more extensive web. Notoriety calculations and capacity methods help appropriate the substance in manners that augment offload proficiency. The framework decreases the interest on upstream system limit and aides Netflix work all the more intimately with the ISP systems that have its traffic.

  1. The Cloud Service

The transfer improved Netflix's adaptability and administration accessibility and the speed by which the organization could discharge new substance, highlights, interfaces and collaborations. It additionally opened up the limit of designers, cut the expenses of gushing, definitely improved accessibility and included the experience and ability of AWS (Macaulay 2018). The cost model permits Netflix to complete a ton of experimentations, given that they pay for what they use.

  1. Message Security Layer

Netflix serves sound and video to a great many gadgets and supporters over the globe. Every gadget has its own one of a kind equipment and programming, and contrasting security properties and abilities. The correspondence between these gadgets and Netflix's servers must be verified to ensure both the endorsers and the administration (Netflix Technology Blog 2014).

When they originally propelled the Netflix gushing administration, they utilized a mix of HTTPS and a homegrown security component called NTBA to give that security. Notwithstanding, after sometime this mix began showing developing agonies. With the appearance of HTML5 and the Media Source Extensions and Encrypted Media Extensions we required something new that would be perfect with that stage. They accepted this as an open door to address a large number of the inadequacies of the prior innovation. The Message Security Layer (MSL) was conceived from these double concerns.

  1. MSL Protocols

A common MSL message comprises of a header and at least one application payload pieces. Each piece is exclusively ensured which enables the sender and beneficiary to process application information as it is transmitted. A message stream may stay open uncertainly, permitting expansive time holes between lumps whenever wanted.

MSL has pluggable verification and may use any number of gadget and client validation types for the underlying message. The underlying message will give confirmation, trustworthiness insurance, and encryption if the gadget validation type underpins it. Future messages will utilize session keys built up because of the underlying correspondence. In the event that the beneficiary experiences a blunder while accepting a message, it will react with a mistake message. Error messages comprise of a header that shows the sort of mistake that happened. Endless supply of the mistake messages the first sender can endeavour to recuperate and retransmit the first application information. For instance, if the message beneficiary trusts one side or the other is utilizing off base session keys the mistake will show that new session keys ought to be consulted without any preparation. Or then again if the message beneficiary trusts the gadget or client qualifications are off base the blunder will demand the sender re-confirm utilizing new certifications.

To limit arrange round-trips MSL endeavours to perform confirmation, key exchange, and recharging tasks while it is additionally transmitting application information. Subsequently, MSL does not force any extra system round treks and just negligible information overhead. This may not generally be conceivable in which case a MSL handshake should initially happen, after which delicate information, for example, client accreditations and application information might be transmitted. When session keys have been built up, they might be reused for future correspondence. Session keys may likewise be persevered to permit reuse between application executions. In a believed administration arrange, the session keys coming about because of a key exchange with one server can be utilized with every single other server.

  • Network Protocols

Netflix utilizes Transmission Control Protocol/Internet Protocol (TCP) as opposed to User Datagram Protocol (UDP). On-request video spilling meets with TCP in their temperament. To begin with, video gushing embraces pre-getting and buffering to accomplish smooth play-out. TCP gives such (organize) support, just as the solid transmission ensure for no loss of casing - however an edge could even now miss the playout due date and gets disposed of, notwithstanding.

Second, TCP's data transfer capacity testing and clog control will endeavour to utilize the majority of the accessible transmission capacity between the server and customer, getting content as fast as could be expected under the circumstances while being cordial to other (TCP) traffic on similar connections.

Then again, live video spilling picks in UDP, in light of the fact that little pre-getting should be possible in live gushing and the more the buffering the more noteworthy the video play-out deferral. Since UDP serves just the most fundamental transport layer usefulness, it will be utilized mutually with other application-layer, video-explicit conventions, for example, RTSP to perform video gushing. Firewalls (from ventures, ISPs) loathe these conventions (in contrast to TCP, these conventions can persistently devour profitable transmission capacity), making the brought video traffic hard to cross through or being throttled.

So as to convey recordings, stages embrace/lease Content Delivery Networks (CDN). The vast majority of the CDN servers (for example Akamai's) were initially and right now designed to help web benefits as their essential course. In this manner, spilling video over HTTP works out of the crate without setting up committed servers, and the majority of the firewalls won't square HTTP traffic. Truth be told, Dynamic Adaptive Streaming over HTTP (DASH) has turned into a typical practice. In spite of the fact that in principle HTTP can be embodied in different conventions, these conventions still need to give dependable exchange (as what typical HTTP presumes) blocks UDP. Remarkably, Netflix fabricates their own CDN.

Netflix utilizes some encryption to anticipate burglary of recordings. It's simpler to do this for TCP stream due to ensured receipt of fragments, and in the right request. With UDP, it's a lot harder to do that since the informational index is constrained to each datagram. With TCP association, it's most likely simpler to flag encryption key changes at generally fixed interims to guarantee better security.

The most grounded explanation behind Netflix to utilize TCP is it's very simple to screen the transmission capacity between the source and recipient, and adjust the image quality dependent on that, since they possess both end-applications. Netflix doesn't enable an outsider player to playback their stream; It just works with their exclusive application. At a more extensive systems administration level TCP is better for variable transfer speeds that happen on the Internet since it has a self-timing instrument, driven by ACKs, to adjust to accessible transmission capacity. Present day switches all actualize blockage shirking utilizing RED/WRED calculation which truly functions admirably with TCP to consistently spread the weight of decreased transmission capacity because of clog among a great many progressing streams so a solitary stream doesn't see a lot of debasement. RED and UDP don't function admirably, to the extent it's known.

  • Devices

Open Connect Appliances are ordinarily arranged in a system. In the event that an individual is an Open Connect ISP accomplice, Netflix works intimately with them to decide the ideal setup for their specific needs. OCAs are coordinated store apparatuses, implying that the way in which traffic is coordinated to the machine is resolved unequivocally by you and by Netflix, not by the apparatus itself. An OCA just serves customers at IP delivers that you promote to the OCA by means of a BGP session. As such, traffic is just conveyed from your inserted OCAs to the client prefixes that you expressly report to them, as depicted in the accompanying areas. Accordingly, you as the ISP accomplice have full power over the systems that the apparatuses will serve. BGP sessions are built up among appliance(s) and the nearest associated switch. On the off chance that content is mentioned that isn't contained on an implanted OCA, the customer demand is coordinated to the nearest Netflix content site by means of peering (if present) or through travel.

  1. Applications

Netflix's applications and robotized observing continually check the execution and dormancy of administrations. On account of utilizations, they are composed to call the administrations non-concurrently, so that on the off chance that one comes up short, the application does not hang, yet proceeds onward with a little piece missing or with marginally stale reserved information (Golden 2012). The checking component continually watches administration execution and, on the off chance that it watches heinous differences it will start a lot of explicit computerized steps. In the event that the administration execution issue continues, the framework will raise alarms to guarantee that human consideration is coordinated to the issue.


Netflix Investors 2018, Netflix - Overview - Long-Term View, [online], Available at: [Accessed 30 Apr. 2019].

Willemsen, R 2016, Why Netflix Went From DVD Services To Internet Streaming. [online] Available at: [Accessed 30 Apr. 2019].

Macaulay, T 2018, 10 Years On: How Netflix completed a historic cloud migration with AWS. [online] ComputerworldUK. Available at: [Accessed 30 Apr. 2019].

Golden, B 2012, Cloud Computing Done the Netflix Way. [online] CIO. Available at: [Accessed 30 Apr. 2019].

Sclater, I, 2013, Netflix streaming bandwidth - use a speed test to optimize. [online] Bandwidth Place. Available at: [Accessed 30 Apr. 2019].

Netflix Technology Blog 2014, Message Security Layer. [online] Medium. Available at: [Accessed 30 Apr. 2019].

Netflix 2019, Network Configuration | Open Connect. [online] Available at: [Accessed 30 Apr. 2019].