Table of Contents

Netflix’s Overall Architecture

The information in this articles was gathered from numerous open-source projects and engineering blogs at Netflix. In this blog, we will study about System Design Netflix. We’ve all watched a variety of movies and web series on Netflix, but this post will spark a lot of discussion since it will show us what goes on behind the scenes that makes Netflix what it is. We’ll start with the fundamentals, then delve into the technicalities of Netflix’s system design and the end-to-end processes involved in providing content at scale.

First and foremost, what is Netflix?

Netflix, Inc. is an American over-the-top entertainment and production firm based in Los Gatos, California. Reed Hastings and Marc Randolph established Netflix in 1997 in Scotts Valley, California.

Web and mobile:

Netflix has developed native mobile apps using Kotlin and Swift. It makes use of React for its online application.

Graph QL :

Netflix uses GraphQL for frontend/server communication.

Backend services:

ZUUL, Eureka, the Spring Boot framework, and other technologies are used by Netflix.

Databases:

Cassandra, CockroachDB, EV cache, and other databases are used by Netflix.

Messaging and Streaming:

Netflix utilizes Fink and Apache Kafka for messaging and streaming scenarios.

Video Storage:

Netflix stores its videos on S3 and Open Connect servers.

Data processing:

Tableau is used to show the data after it has been processed using Flink and Spark. Information from structured data warehouses is processed using Redshift.