쉐도잉 연습: NGINX Explained - What is Nginx - 영상으로 영어 말하기 배우기

By the end of this video, you will know not only what Nginx is,

but also why it was created and what it's used for with real life examples.

Back in the day when the web was still simple with less users, the basic use case was a browser requested a web page from one web server.

The web server was a server machine that had a software installed on it

that assembled the page and sent it back to the browser, which then displayed it to the user a piece of software

that runs on a server machine and can respond to requests from a browser.

And that web server software, that was Nginx, a piece of software that runs on a server machine and can respond to requests from a browser.

Then web became popular, so you had thousands or millions of requests per website.

Imagine one single server handling millions of requests.

That's way over the technical limit of a server software.

Well, we need a few more servers to handle that load.

So we added 10 Nginx web servers.

But now we need something that determines where requests from the browser and which one of those 10 servers will handle them.

And that's where load balancing comes in.

So the same Nginx web server becomes a load balancer that proxies the requests to those 10 web servers.

And by the way, the word proxy means to do something on someone else's behalf.

So it accepts the browser requests on behalf of the web servers.

like a concierge

and then distributes the load among the web servers now how does it distribute the load

that depends on whichever algorithm was configured on it it could

be a simple logic such as just whichever server is least busy gets the request

or it could be a round robin which is a popular algorithm

that basically distributes the requests equally in a cyclical manner So very simple load balancing logic.

So now we have Nginx as web server software.

and the proxy as well and

that load balancing is just one of the functionalities of nginx proxy

so it's the same server and technology but with a different task now

so what are those other features or functionalities of a proxy

Imagine New York Times article comes out and millions of people open it on their laptops in the browser.

Now imagine every time the request landed with one of the web servers that assembled the response,

like put the images together, get them from a database, put text and paragraphs and everything together, edit all the links, sent it back as a response.

to assemble this article, get all the data from a database, put the text and links and everything together once and store it.

It's a static article, it's not going to change, right?

So just keep one final copy and send it to everyone who requests it.

That's caching functionality and it is another main feature of Nginx Proxy server.

So you can configure caching on Nginx Proxy

so you don't have to hit the database or the web servers every time a request comes in.

It will just return that cached file.

Now imagine we have 100 servers of an online banking application or a social network like Facebook.

That makes those servers a pretty juicy target for hackers.

They all want to hack into your servers and get the treasure, which is payment data, personal data, passwords, and so on.

Now imagine you exposed all 100 servers to public access.

So basically all those requests can directly hit each of the web servers.

hackers so much easier.

They would need to find just one issue in one of those hundred servers, and they could potentially break into your entire system.

Because all your servers are publicly accessible directly, they can just ping the hell out of them

and probe them until they find an issue or an entry because you forgot to update a library or a software package, and they can hack your web server application.

So you have to worry about absolutely perfectly securing hundred servers.

Instead, we just give them one server.

That is the only one that's publicly accessible.

You can put all your tightest security efforts on one server instead of 100 servers.

And this way having one entry point, which is the proxy, as publicly accessible entry point,

reduces the security attack surface tremendously and basically acts like a shield or security layer before all those web servers.

So in addition to load balancing and caching,

a very, very important functionality of a proxy is an edit security for your web servers.

Now talking about security, I mentioned that since we have one entry point, we can focus all our efforts to securing that one proxy server in all aspects.

And one important security measure is encrypted communication.

So front -end will send encrypted message to the proxy, which means even if an attacker sees that traffic on user's browser or during the transmission, they can't read it.

Only the proxy server can decrypt it.

But again, for edit security in many systems, proxy that acts as a shield,

a security shield, will simply pass on that encrypted message to the web servers and the web server will decrypt it.

itself which is actually a better security practice.

So here the functionality of a proxy is to be able to accept encrypted traffic with SSL encryption.

So you can configure your proxy to deny any requests that is not encrypted and only accept encrypted requests.

Now imagine Netflix, which by the way uses Nginx in its backend.

And as we know, Netflix has millions of users, so it's getting millions of requests for videos on its web servers.

And let's say it's an evening in New York, millions of people come home after work, All at the same time,

they switch on Netflix and start watching the most popular series at that time.

That means suddenly at the very same time, millions of requests for a high quality video is sent to Netflix.

So in this case, imagine

that Nginx proxy server would have to send back the entire high quality video to millions of users at once.

That's a lot of bandwidth.

internet cables all the way to the TVs of millions of viewers.

That's where compression helps nginxproxy can also be configured to compress large images

or video files to save bandwidth both on the side of the clients

so people who are receiving those large files

but also on the server side who is sending all

that content so it arrives faster and it uses up less of your internet bandwidth

and as part of it it also supports sending responses in chunks instead of the entire

part of the video and then by the time you have watched the first half, the second half of the video has been sent over to you as well.

So these are all the functionalities that you can configure for Nginx as a proxy server.

Now, you may be thinking, how do you make Nginx do all these things?

How do you configure them?

How do you tell Nginx whether it should act as a web server or a proxy server?

And how do you configure all this caching and SSL traffic and all this stuff?

Well, that's where Nginx configuration file comes in, which lets you define all this configuration with so -called directives.

This is where you can define whether you want your Nginx to be a web server or a proxy server,

simply by configuring whether it should forward the traffic to other web servers or whether it should handle it itself.

You can configure which port you want Nginx server to listen on.

This is an example of a simple web server configuration

that listens on port 80

and with location basically defines from where in the file system it should serve those static files back but as we learned,

communicating on port 80 or HTTP port is insecure.

Instead, we want to encrypt all the communication.

And you can configure

that easily in Nginx to route any traffic coming on port 80 to HTTPS by sending those requests to HTTPS endpoint.

key and the private key for the SSL communication and it listens on the HTTPS port 443.

So that's a simple configuration that allows you to tweak Nginx to handle requests like that.

You also have its own configuration to configure load balancing to multiple backend servers

100

and within that configuration you can also define which load balancing algorithm to use like select the least which as I said,

101

just equally distributes the load in a cyclical order between those servers.

102

You also have the caching configuration with multiple different elements, like how long the cache should be stored before it's refreshed and so on.

103

And as you see, the configuration of all these functionalities is pretty straightforward, and it's also pretty granular.

104

Like you can do tons of different configurations with Nginx, directives in this list here,

105

which is a pretty huge list, and you see the configurations for proxy functionalities have proxy prefix, so you can differentiate them as well.

106

Now, Nginx is very flexible, as you see, and super fast as well.

107

So it became very popular in containers as well

108

and made its way as one of the most popular solutions for Kubernetes Ingress Controller functionality.

109

Ingress Controller is essentially a proxy with advanced load balancing functionality, but for Kubernetes.

110

So what Nginx was doing for simple web servers, it's now doing for Kubernetes Cluster in the form of Ingress Controller.

111

proxy and load balancer that receives the incoming traffic first and then based on the configuration that we define,

112

forwards it to the right service inside the cluster.

113

Now, this load balancing configuration as well as the logic is more advanced and more Kubernetes specific, but the idea is pretty much the same.

114

And I actually have full videos on Ingress and Ingress controller and how to configure it.

115

You can watch on my channel.

116

In fact, I create these tutorials regularly on a lot of interesting technology.

117

So if you want to educate yourself in tech, make sure to subscribe and activate notification to get those new tutorial videos.

118

Now there are actually many English controller implementations out there for Kubernetes but Nginx is one of the most popular ones.

119

And I have actually used Nginx Ingress Controller in most of my projects as well.

120

Now, some of you may be thinking, doesn't each cloud platform have its own load balancer?

121

Why do I need Nginx as a load balancer?

122

Well, you actually need both.

123

Nginx Ingress Controller, which acts as a load balancer, is used inside the cluster.

124

accessible so you can't access the nginx ingress controller directly from the browser it actually lives inside the cluster network

125

and forwards the requests internally

126

so who is getting the requests from public what is the

127

public entry point for the browser requests that's the cloud load balancer like aws elb for example

128

which then forwards that request to the ingress controller inside the very important security layer to those requests.

129

So the cluster component is never directly exposed to public access.

130

Instead, every request comes from the cloud load balancer, which then forwards it to the Ingress controller within the cluster,

131

which then routes the traffic based on intelligent logic to different applications within the cluster.

132

And with intelligent routing, what I mean is, of sub -segments or microservices, for example, you can configure your English controller.

133

So if the request URL includes Online cart, it routes the traffic to online cart microservice.

134

If it includes payment, it routes the traffic to payment service and so on.

135

Now, some of you who've been in IT for a little longer may have worked with Apache web server.

136

So what's the difference between Apache web server and Nginx web server?

137

Well, not much, actually.

138

Nginx and Apache web servers do pretty much the same thing.

139

Just like Nginx, Apache also used to be a basic web server,

140

extended its functionality as a proxy and it has all these benefits and functionalities of a proxy that we discussed.

141

Apache was actually already widely used when Nginx was created and the major benefit of Nginx was that it was faster,

142

more lightweight and definitely had an advantage when it came to serving huge amounts of static files.

143

Plus, as you saw, it has a pretty easy configuration as well.

144

And Nginx also became more popular in the container world.

145

Now, I hope you got a clear overview of what Nginx is

146

and hope I've answered all the questions you may have had while learning about Nginx.

147

And with that, thank you for watching and see you in the next video.

📺 같은 채널

Redis Crash Course - the What, Why and How to use Redis as your primary database

Business EnglishUniversity StudentsWorking Adults

✨ 추천 영상

176 문장

Every Networking Concept Explained | Networking 101 (2026)

Business EnglishUniversity StudentsWorking Adults

258 문장

Amply Công Suất Lớn Nhất | NEXO NXAMP 4x4 | Power 16000W | Kích thước 4U

Business EnglishUniversity StudentsWorking Adults

49 문장

Next JS Interview Questions and Answers 2026 | Top 20 Most Asked Questions

Business EnglishInterview EnglishUniversity Students

333 문장

Master n8n Triggers in 20 Minutes – Automate Anything

Business EnglishUniversity StudentsWorking Adults

202 문장

Proxy vs Reverse Proxy Server Explained

Business EnglishUniversity StudentsWorking Adults

85 문장

AI Can Write Code. And That’s the Problem.

Business EnglishUniversity StudentsWorking Adults

177 문장

Mini Project - Implementing a Simple Web Identity Federation Application

Business EnglishUniversity StudentsWorking Adults

345 문장

What the heck is the event loop anyway? | Philip Roberts | JSConf EU

Business EnglishUniversity StudentsWorking Adults

150 문장

Parallel Pump Operation

Business EnglishUniversity StudentsWorking Adults

74 문장

LangChain in 5 Minutes (Explained Clearly)

Business EnglishUniversity StudentsWorking Adults

쉐도잉이란? 영어 실력을 빠르게 키우는 과학적 방법

쉐도잉(Shadowing)은 원래 전문 통역사 훈련을 위해 개발된 언어 학습 기법으로, 다언어 학자인 Dr. Alexander Arguelles에 의해 대중화된 방법입니다. 핵심 원리는 간단하지만 매우 강력합니다: 원어민의 영어를 들으면서 1~2초의 짧은 지연으로 즉시 소리 내어 따라 말하는 것——마치 '그림자(shadow)'처럼 화자를 따라가는 것입니다. 문법 공부나 수동적인 청취와 달리, 쉐도잉은 뇌와 입 근육이 동시에 실시간으로 영어를 처리하고 재현하도록 훈련합니다. 연구에 따르면 이 방법은 발음 정확도, 억양, 리듬, 연음, 청취력, 말하기 유창성을 크게 향상시킵니다. IELTS 스피킹 준비와 자연스러운 영어 소통을 원하는 분들에게 특히 효과적입니다.

섀도잉 방법: 단계별 전체 가이드 읽기 →

쉐도잉 연습: NGINX Explained - What is Nginx - 영상으로 영어 말하기 배우기

Redis Crash Course - the What, Why and How to use Redis as your primary database

What is Docker? Docker container concept explained || Docker Tutorial 1

Every Networking Concept Explained In 20 Minutes

CI/CD Explained in 5 Minutes

Microservices explained - the What, Why and How?

Kafka Tutorial for Beginners | Everything you need to get started

If I would start DevOps from 0 - How would I start and what would I learn

Every Networking Concept Explained | Networking 101 (2026)

Amply Công Suất Lớn Nhất | NEXO NXAMP 4x4 | Power 16000W | Kích thước 4U

Next JS Interview Questions and Answers 2026 | Top 20 Most Asked Questions

Master n8n Triggers in 20 Minutes – Automate Anything

Proxy vs Reverse Proxy Server Explained

AI Can Write Code. And That’s the Problem.

Mini Project - Implementing a Simple Web Identity Federation Application

What the heck is the event loop anyway? | Philip Roberts | JSConf EU

Parallel Pump Operation

LangChain in 5 Minutes (Explained Clearly)

이 수업에 대하여

핵심 어휘 & 구문

연습 팁

쉐도잉이란? 영어 실력을 빠르게 키우는 과학적 방법