Shadowing Practice: NGINX Explained - What is Nginx - Learn English Speaking with Video
בחר מצב תרגול
כל מצב פותח חדר תרגול במסך מלא.
147 משפטים
אם המשפטים קצרים או ארוכים מדי, לחץ על ערוך כדי להתאים אותם.
1
By the end of this video, you will know not only what Nginx is,
2
but also why it was created and what it's used for with real life examples.
3
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.
4
The web server was a server machine that had a software installed on it
5
that assembled the page and sent it back to the browser, which then displayed it to the user a piece of software
6
that runs on a server machine and can respond to requests from a browser.
7
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.
8
Then web became popular, so you had thousands or millions of requests per website.
9
Imagine one single server handling millions of requests.
10
That's way over the technical limit of a server software.
11
Well, we need a few more servers to handle that load.
12
So we added 10 Nginx web servers.
13
But now we need something that determines where requests from the browser and which one of those 10 servers will handle them.
14
And that's where load balancing comes in.
15
So the same Nginx web server becomes a load balancer that proxies the requests to those 10 web servers.
16
And by the way, the word proxy means to do something on someone else's behalf.
17
So it accepts the browser requests on behalf of the web servers.
18
like a concierge
19
and then distributes the load among the web servers now how does it distribute the load
20
that depends on whichever algorithm was configured on it it could
21
be a simple logic such as just whichever server is least busy gets the request
22
or it could be a round robin which is a popular algorithm
23
that basically distributes the requests equally in a cyclical manner So very simple load balancing logic.
24
So now we have Nginx as web server software.
25
and the proxy as well and
26
that load balancing is just one of the functionalities of nginx proxy
27
so it's the same server and technology but with a different task now
28
so what are those other features or functionalities of a proxy
29
Imagine New York Times article comes out and millions of people open it on their laptops in the browser.
30
Now imagine every time the request landed with one of the web servers that assembled the response,
31
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.
32
to assemble this article, get all the data from a database, put the text and links and everything together once and store it.
33
It's a static article, it's not going to change, right?
34
So just keep one final copy and send it to everyone who requests it.
35
That's caching functionality and it is another main feature of Nginx Proxy server.
36
So you can configure caching on Nginx Proxy
37
so you don't have to hit the database or the web servers every time a request comes in.
38
It will just return that cached file.
39
Now imagine we have 100 servers of an online banking application or a social network like Facebook.
40
That makes those servers a pretty juicy target for hackers.
41
They all want to hack into your servers and get the treasure, which is payment data, personal data, passwords, and so on.
42
Now imagine you exposed all 100 servers to public access.
43
So basically all those requests can directly hit each of the web servers.
44
hackers so much easier.
45
They would need to find just one issue in one of those hundred servers, and they could potentially break into your entire system.
46
Because all your servers are publicly accessible directly, they can just ping the hell out of them
47
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.
48
So you have to worry about absolutely perfectly securing hundred servers.
49
Instead, we just give them one server.
50
That is the only one that's publicly accessible.
51
You can put all your tightest security efforts on one server instead of 100 servers.
52
And this way having one entry point, which is the proxy, as publicly accessible entry point,
53
reduces the security attack surface tremendously and basically acts like a shield or security layer before all those web servers.
54
So in addition to load balancing and caching,
55
a very, very important functionality of a proxy is an edit security for your web servers.
56
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.
57
And one important security measure is encrypted communication.
58
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.
59
Only the proxy server can decrypt it.
60
But again, for edit security in many systems, proxy that acts as a shield,
61
a security shield, will simply pass on that encrypted message to the web servers and the web server will decrypt it.
62
itself which is actually a better security practice.
63
So here the functionality of a proxy is to be able to accept encrypted traffic with SSL encryption.
64
So you can configure your proxy to deny any requests that is not encrypted and only accept encrypted requests.
65
Now imagine Netflix, which by the way uses Nginx in its backend.
66
And as we know, Netflix has millions of users, so it's getting millions of requests for videos on its web servers.
67
And let's say it's an evening in New York, millions of people come home after work, All at the same time,
68
they switch on Netflix and start watching the most popular series at that time.
69
That means suddenly at the very same time, millions of requests for a high quality video is sent to Netflix.
70
So in this case, imagine
71
that Nginx proxy server would have to send back the entire high quality video to millions of users at once.
72
That's a lot of bandwidth.
73
internet cables all the way to the TVs of millions of viewers.
74
That's where compression helps nginxproxy can also be configured to compress large images
75
or video files to save bandwidth both on the side of the clients
76
so people who are receiving those large files
77
but also on the server side who is sending all
78
that content so it arrives faster and it uses up less of your internet bandwidth
79
and as part of it it also supports sending responses in chunks instead of the entire
80
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.
81
So these are all the functionalities that you can configure for Nginx as a proxy server.
82
Now, you may be thinking, how do you make Nginx do all these things?
83
How do you configure them?
84
How do you tell Nginx whether it should act as a web server or a proxy server?
85
And how do you configure all this caching and SSL traffic and all this stuff?
86
Well, that's where Nginx configuration file comes in, which lets you define all this configuration with so -called directives.
87
This is where you can define whether you want your Nginx to be a web server or a proxy server,
88
simply by configuring whether it should forward the traffic to other web servers or whether it should handle it itself.
89
You can configure which port you want Nginx server to listen on.
90
This is an example of a simple web server configuration
91
that listens on port 80
92
and with location basically defines from where in the file system it should serve those static files back but as we learned,
93
communicating on port 80 or HTTP port is insecure.
94
Instead, we want to encrypt all the communication.
95
And you can configure
96
that easily in Nginx to route any traffic coming on port 80 to HTTPS by sending those requests to HTTPS endpoint.
97
key and the private key for the SSL communication and it listens on the HTTPS port 443.
98
So that's a simple configuration that allows you to tweak Nginx to handle requests like that.
99
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.
הורד אפליקציה
כל מה שאתה צריך כדי לדבר בשטף
הגיית AIציון לכל משפט
תרגול IPAשלוט בכל צליל
אוצר מיליםבנה את מאגר המילים שלך
משחק אוצר מיליםלמד תוך כדי משחק
אותו ערוץ
C1Redis Crash Course - the What, Why and How to use Redis as your primary database
Daily ConversationUniversity StudentsWorking Adults
C12
What is Docker? Docker container concept explained || Docker Tutorial 1
Daily ConversationUniversity StudentsWorking Adults
C11
Every Networking Concept Explained In 20 Minutes
Daily ConversationUniversity StudentsWorking Adults
B21
CI/CD Explained in 5 Minutes
Business EnglishUniversity StudentsWorking Adults
C12
Microservices explained - the What, Why and How?
Business EnglishUniversity StudentsWorking Adults
C17
If I would start DevOps from 0 - How would I start and what would I learn
University StudentsWorking Adults
C12
Kafka Tutorial for Beginners | Everything you need to get started
Business EnglishUniversity StudentsWorking Adults
FOR YOU
המלץ על סרטון
C13
58 משפטים
Proxy vs Reverse Proxy (Real-world Examples)
Daily ConversationUniversity StudentsWorking Adults
C130
26 משפטים
Docker in 100 Seconds
American AccentBusiness EnglishUniversity StudentsWorking Adults
C11
168 משפטים
The Essential Main Ideas of Neural Networks
Business EnglishUniversity StudentsWorking Adults
C12
51 משפטים
Cloud Models - CompTIA Network+ N10-009 - 1.3
Business EnglishUniversity StudentsWorking Adults
C16
45 משפטים
The plan to break apart Google... RIP Chrome
American AccentBusiness EnglishDaily ConversationUniversity Students
C12
95 משפטים
API Gateways in System Design Interviews w/ Ex-Meta Staff Engineer
Business EnglishInterview EnglishUniversity Students
C11
309 משפטים
Claude Code: The Advanced Guide (99% of Devs Skip These Features)
Business EnglishUniversity StudentsWorking Adults
C12
195 משפטים
JavaScript Visualized - Event Loop, Web APIs, (Micro)task Queue
Business EnglishUniversity StudentsWorking Adults
C16
22 משפטים
Server-side tracking explained in 100 seconds || What is server-side GTM?
Business EnglishUniversity StudentsWorking Adults
C13
260 משפטים
【TED】優れたリーダーはどうやって行動を促すか/サイモン・シネック （日本語字幕）
Business EnglishDaily ConversationUniversity Students
C16
49 משפטים
What Are Microservices Really All About? (And When Not To Use It)
Business EnglishUniversity StudentsWorking Adults
אוצר מילים והערות הגייה לשיעור הזה
שיעור הדיבור הזה ברמה C1 מבוסס על הסרטון “NGINX Explained - What is Nginx”. המילים שחוזרות הכי הרבה: server, nginx, web, request, proxy. בסרטון הזה יש 147 משפטים ו-2151 מילים לתרגול Shadowing. הדיבור נמשך 14:32. הדובר שומר על קצב יציב של כ-148 מילים בדקה, קצב נוח לתרגול Shadowing. רק 77% מהמילים נמצאות בין 3,000 המילים הנפוצות ביותר באנגלית, כך שאוצר המילים מאתגר.
אוצר מילים מרכזי בסרטון הזה
15 המילים המתקדמות ביותר בסרטון, עם ההגייה והמשמעות שלהן:
| מילה | הגייה | משמעות |
|---|---|---|
| proxy שם עצם | /ˈpɹɑk.si/ | שָׁלִיחַ |
| encrypt פועל | /ɪnˈkɹɪpt/ | הצפין |
| cache שם עצם | /kæʃ/ | מִצְבּוֹר, מַחְבּוֹא |
| distribute פועל | /dɪˈstɹɪbjuːt/ | חילק |
| bandwidth שם עצם | /ˈbændwɪdθ/ | רוחב פס |
| assemble פועל | /əˈsɛm.bəl/ | אסף |
| algorithm שם עצם | /ˈælɡəɹɪðm̩/ | אַלגוֹרִיתְם |
| cart שם עצם | /kɑɹt/ | עֲגָלָה |
| container שם עצם | /kənˈteɪ.nəɹ/ | מיכל |
| prefix שם עצם | /ˈpɹiːfɪks/ | תְּחִלִּית |
| juicy שם תואר | /ˈd͡ʒuːsi/ | עסיסי |
| viewer שם עצם | /ˈvju.ɚ/ | צוֹפֶה |
| notification שם עצם | /ˌnoʊtɪfɪˈkeɪʃn̩/ | הוֹדָעָה |
| educate פועל | /ˈɛd͡ʒ.əˌkeɪt/ | חִינֵּךְ |
| probe שם עצם | /pɹoʊb/ | זונדה |
Phrasal verbs שתשמעו
| מילה | הגייה | משמעות |
|---|---|---|
| come out פועל | /ˌkʌm ˈaʊt/ | יָצָא |
דקדוק בסרטון הזה
המבנים שהדובר משתמש בהם הכי הרבה, עם המילים המדויקות מהסרטון:
| מבנה | בסרטון |
|---|---|
| סביל (Passive voice) be + past participle — הדגש הוא על מה שקורה, לא על מי שעושה את הפעולה | was created · was configured · is encrypted |
| משפטי זיקה (Relative clauses) who / which + clause — מידע נוסף על אדם או דבר | robin which is · everyone who requests · treasure, which is |
| הווה מושלם (Present perfect) have/has + past participle — פעולה שקרתה בעבר ועדיין יש לה חשיבות או השפעה עכשיו | have watched · have actually used · who've been |
הגייה ששווה לשים לב אליה
הדובר משתמש ב-6 קיצורים וצורות מקוצרות, כמו can't, doesn't, don't. אמרו אותם בצורה הקצרה, כפי שאתם שומעים אותם.
- הצלילים של “th”: bandwidth /ˈbændwɪdθ/, algorithm /ˈælɡəɹɪðm̩/
- הצלילים של “sh” ו-“zh”: configuration /kənˌfɪɡ.əˈɹeɪ̯.ʃən/, cache /kæʃ/, concierge /ˌkɑnsiˈɛɹʒ/, encryption /ɪnˈkɹɪpʃən/, differentiate /dɪf.əˈɹɛn.ʃi.eɪt/
- מילים ארוכות — שימו לב להטעמה: configuration /kənˌfɪɡ.əˈɹeɪ̯.ʃən/, differentiate /dɪf.əˈɹɛn.ʃi.eɪt/, internally /ɪnˈtɜːnəli/, notification /ˌnoʊtɪfɪˈkeɪʃn̩/
צלילים שדוברי עברית מתקשים בהם:
- /w/ — שפתיים מעוגלות, לא /v/: bandwidth /ˈbændwɪdθ/, whichever /wɪt͡ʃˈɛvɚ/, lightweight /ˈlaɪt.weɪt/, straightforward /ˌstɹeɪtˈfɔː(ɹ)wə(ɹ)d/, password /ˈpæs.wɜɹd/
- /æ/ — פתוח יותר מה-“אֶ” העברית, לא כמו “a” ב-“cup”: balancer /ˈbæ.lən.sɚ/, cache /kæʃ/, bandwidth /ˈbændwɪdθ/, algorithm /ˈælɡəɹɪðm̩/, static /ˈstæt.ɪk/
- /r/ — הלשון לא נוגעת בשום מקום, לא ה-“ר” הגרונית: proxy /ˈpɹɑk.si/, configure /kənˈfɪɡə(ɹ)/, configuration /kənˌfɪɡ.əˈɹeɪ̯.ʃən/, ingress /ˈɪŋɡɹɛs/, browser /ˈbɹaʊ.zəɹ/
איך לתרגל עם הסרטון הזה
- הקשיבו לכל הסרטון פעם אחת בלי לדבר, ורשמו את המילים שאתם לא מכירים.
- תרגלו Shadowing משפט אחר משפט במהירות רגילה, וחזרו על כל משפט עד שהקצב שלכם תואם את הדובר.
- הקליטו את עצמכם והשוו למקור, תוך תשומת לב למילים כמו proxy, encrypt, cache.
מהי טכניקת השאדואינג?
שאדואינג היא טכניקת למידת שפה מבוססת מדע שפותחה במקור להכשרת מתורגמנים מקצועיים ופופולרית על ידי הפוליגלוט ד"ר אלכסנדר ארגואלס. השיטה פשוטה אך עוצמתית: אתה מקשיב לאודיו באנגלית ילידית וחוזר עליו בקול רם מיד — כמו צל העוקב אחרי הדובר עם עיכוב של 1–2 שניות בלבד. בניגוד להאזנה פסיבית או תרגילי דקדוק, שאדואינג מכריח את המוח והשרירים בפה לעבד ולשחזר דפוסי דיבור אמיתיים בו זמנית. מחקרים מראים שזה משפר משמעותית את דיוק ההגייה, האינטונציה, הקצב, הדיבור המחובר, הבנת השמיעה ושטף הדיבור — מה שהופך אותו לאחת השיטות היעילות ביותר להכנה לIELTS Speaking ולתקשורת באנגלית בעולם האמיתי.