Shadowing Practice: I Bet Nobody Has Ever Explained the Backend Ecosystem Like This Before - Learn English Speaking with Video
בחר מצב תרגול
כל מצב פותח חדר תרגול במסך מלא.
164 משפטים
אם המשפטים קצרים או ארוכים מדי, לחץ על ערוך כדי להתאים אותם.
1
If you've ever searched for a back -end roadmap, you've probably seen an overwhelming list of technologies like
2
Spring Boot, Docker, Kubernetes, Redis, Kafka, PostgreSQL, Jenkins, AWS, Prometheus, and many more.
3
Looking at it for the first time, it's easy to wonder, do back -end engineers really need to learn all of this?
4
The short answer is no. The goal isn't to memorize every technology.
5
The goal is to understand why each category exists.
6
Once you understand the problem a technology solves, learning another tool in the same category becomes much easier.
7
So instead of going through a roadmap and explaining one technology after another, let's do something different.
8
Let's follow a single request and see how all these technologies work together.
9
Imagine you're shopping on an e -commerce website.
10
You find a laptop you like, add it to your cart, enter your delivery address, complete the payment, and click place order.
11
From your perspective, it was just one click.
12
But behind that single click, an entire ecosystem starts working together.
13
Let's follow that journey.
14
The first stop is usually a reverse proxy, such as NGINX.
15
It receives every incoming request from users and forwards it to the appropriate backend service based on the type of request.
16
For example, a request to view products may be forwarded to one backend application, while a payment request may be forwarded to another.
17
Users usually don't communicate with backend applications directly.
18
Every request first passes through the reverse proxy.
19
The request has now reached the backend.
20
So what exactly is the backend?
21
The backend is simply the part of the application that runs on a server.
22
Unlike the frontend, which users can see and interact with, the backend works behind the scenes.
23
It receives requests, applies business rules, communicates with databases and other services, and finally sends a response back to the frontend.
24
You can think of the backend as the brain of the application.
25
Developers build backends using backend frameworks.
26
A framework is simply a collection of tools and pre -built code that helps developers build applications faster without starting from scratch.
27
For example, Java developers commonly use Spring Boot.
28
C Sharp developers often use ASP .NET Core.
29
JavaScript developers might use
30
Express or NestJS.
31
Python developers frequently use FastAPI or Django.
32
The framework changes.
33
The programming language changes.
34
But the backend's responsibility stays exactly the same.
35
Before the backend places your order, it first needs to answer one important question.
36
Who is making this request?
37
Anyone could send a request saying, place an order.
38
The backend must first verify that the request actually came from a logged in user.
39
This process is called authentication.
40
Technologies such as session -based authentication,
41
JWTs, OAuth, and OpenID Connect help applications verify a user's identity securely.
42
If your identity is verified, the backend continues processing the request.
43
If not, the request is rejected immediately, preventing unauthorized users from accessing your account or placing orders on your behalf.
44
Now that the backend knows who you are, it can start processing your request.
45
Suppose you click Place Order.
46
The backend now needs information such as your delivery address, the items in your cart, and your payment details.
47
Where does it get all this information?
48
It gets it from a database.
49
A database is where an application permanently stores its data, customer accounts, products, orders, payments, delivery addresses.
50
All this information is stored in a database, so it is still available even if the application is restarted tomorrow.
51
Popular databases include PostgreSQL, MySQL, SQL Server, and Oracle.
52
You can think of a database as the application's long -term memory.
53
But here's a problem.
54
Imagine millions of users are opening the application every day.
55
Many of them repeatedly request the same information.
56
For example, a customer may open their profile several times a day, or thousands of customers may be viewing the same popular product.
57
If every request goes directly to the database, the database has to do the same work again and again.
58
As the number of users grows, this can become a performance bottleneck.
59
So instead of asking the database every single time, the backend first checks a cache, such as Redis.
60
A cache stores temporary copies of data that applications access frequently.
61
If the required information is already available in the cache, it can be returned almost instantly.
62
If it isn't, the backend retrieves the data from the database, sends it back to the user,
63
and also stores a temporary copy in the cache so future requests become much faster.
64
The important thing to remember is that Redis is not a replacement for the database.
65
The original data always lives in the database.
66
Redis simply keeps temporary copies of frequently accessed data to improve performance and reduce unnecessary database queries.
67
Now let's continue with our order.
68
The backend has successfully saved your order in the database.
69
At this point, from the customer's perspective, the most important job is already done but placing an order usually triggers several additional tasks.
70
The inventory needs to be updated.
71
The warehouse needs to start preparing the package.
72
A shipping request needs to be created.
73
A confirmation email should be sent.
74
Analytic systems need to record the purchase.
75
Should the backend wait for all these tasks to finish before responding to you?
76
Imagine waiting 10 or 15 seconds every time you place an order.
77
That would be a terrible user experience.
78
Instead, the backend immediately responds with, your order has been placed successfully.
79
The remaining tasks are handed over to a message queue, such as Kafka or RabbitMQ.
80
Think of a message queue like people waiting in line at a ticket counter.
81
When you join the queue, you don't get served immediately.
82
You wait for your turn.
83
A message queue works in a similar way.
84
Instead of doing every task immediately, the backend places each task into the queue.
85
Other services pick up these tasks one by one and process them in the background.
86
This allows the application to respond to users quickly while the remaining work continues behind the scenes.
87
That's one of the reasons modern applications feel fast, even though they're performing many operations after you click a single button.
88
Let's take a step back for a moment.
89
So far, we've been following what happens when a customer places an order.
90
But all the software we've discussed so far still needs somewhere to run.
91
That's where Docker comes in.
92
Imagine you've built your back -end application on your laptop.
93
It works perfectly, but when another developer tries to run the same application on their computer,
94
it suddenly doesn't work, because they're using a different version of Java, .NET, or some required libraries are missing.
95
This is a very common problem in software development, and it's often called, it works on my machine.
96
Docker solves this problem.
97
It packages your application together with everything it depends on, such as the runtime, required libraries,
98
and configuration files, into something called a container.
99
You can think of a container as a portable box that carries your application along with everything it needs to run.
100
Because the entire package moves together, the application behaves the same whether it's running on your laptop, a testing server, or a production server.
101
But what happens if your e -commerce application becomes extremely popular?
102
Imagine a big holiday sale where millions of customers are placing orders at the same time.
103
One container is no longer enough to handle all that traffic.
104
You now need hundreds or even thousands of containers running across multiple servers.
105
Some containers may crash.
106
Some need software updates.
107
When traffic suddenly increases, you need more containers.
108
When traffic drops, you don't want to keep unnecessary containers running because they waste resources.
109
Managing all of this manually would be almost impossible.
110
This is exactly the problem Kubernetes solves.
111
Kubernetes automates the management of containers across multiple servers.
112
It starts new containers when more capacity is needed.
113
It restarts containers if they fail.
114
It removes extra containers when traffic decreases.
115
A simple way to remember the difference is this.
116
Docker creates containers.
117
Kubernetes manages them.
118
Now another question naturally comes up.
119
Where are all these servers actually located?
120
Years ago, companies bought physical servers and maintained their own data centers.
121
Today, most companies rent computing resources like servers, storage, and networking from cloud providers such as AWS,
122
Microsoft Azure, or Google Cloud.
123
Instead of buying hardware, companies simply rent the infrastructure they need.
124
These cloud providers supply virtual machines,
125
networking, storage, databases, and many other services that allow modern applications to run at scale.
126
Building an application is only part of the job.
127
Developers are constantly fixing bugs, adding new features, and improving existing functionality.
128
Imagine manually copying every new version of your application to servers every time a small change is made.
129
It would be slow, repetitive, and mistakes would be easy to make.
130
Instead, teams use CI -CD pipelines.
131
CI stands for Continuous Integration, where every code change is automatically built and tested.
132
CD stands for Continuous Delivery or Continuous Deployment, where approved changes are automatically deployed to testing or production environments points.
133
Popular tools include GitHub Actions, GitLab CI, Azure DevOps, and Jenkins.
134
These tools help teams release software faster and with fewer manual errors.
135
Finally, once the application is running in production, engineers need to make sure everything continues working correctly.
136
Is the application responding slowly?
137
Has one of the services crashed?
138
Is CPU or memory usage unusually high?
139
Waiting for customers to report these problems is never a good idea.
140
Instead, engineers continuously monitor their systems using tools such as Prometheus and Grafana.
141
Prometheus collects metrics about your applications and infrastructure, while Grafana visualizes those metrics through dashboards.
142
If something starts going wrong, engineers can often detect the problem and fix it before most customers even notice.
143
Now let's look at the complete picture.
144
From your perspective, placing an order was just one click.
145
Behind that single click, your request passed through a reverse proxy, reached the backend, verified your identity, retrieved data from a database,
146
used a cache to improve performance, handed background work to a message queue, ran inside Docker containers managed by Kubernetes,
147
hosted on cloud infrastructure, automatically deployed through CICD pipelines, and continuously monitored to keep everything running smoothly.
148
That's why back -end roadmaps look so overwhelming at first.
149
They aren't showing unrelated technologies.
150
They're showing different parts of one complete system.
151
Every category exists because it solves a real engineering problem.
152
The specific technologies may change.
153
One company might use
154
Spring Boot, while another uses ASP .NET Core.
155
One team may choose PostgreSQL, while another chooses MySQL.
156
One organization may use Kafka, while another prefers RabbitMQ.
157
The tools are different.
158
The purpose remains the same.
159
So the next time you look at a back -end roadmap, don't ask, which technology should I learn next?
160
Instead, ask, what problem does this technology solve?
161
Once you start thinking that way, back -end development becomes much less about memorizing technology names and much more about understanding how an entire system works.
162
If this video helped you connect the dots, consider subscribing.
163
I've already been covering many of these technologies and tools individually on this channel,
164
and I'll continue breaking down more back -end concepts with simple, practical explanations.
הורד אפליקציה
כל מה שאתה צריך כדי לדבר בשטף
הגיית AIציון לכל משפט
תרגול IPAשלוט בכל צליל
אוצר מיליםבנה את מאגר המילים שלך
משחק אוצר מיליםלמד תוך כדי משחק
אותו ערוץ
FOR YOU
המלץ על סרטון
C11
78 משפטים
How I deploy serverless containers for free
Daily ConversationUniversity StudentsWorking Adults
C12
53 משפטים
Cache Systems Every Developer Should Know
Daily ConversationUniversity StudentsWorking Adults
C14
62 משפטים
"Customer Obsession" Leadership Principle Explained by Amazon CEO Andy Jassy
Daily ConversationUniversity StudentsWorking Adults
C13
58 משפטים
Proxy vs Reverse Proxy (Real-world Examples)
Daily ConversationUniversity StudentsWorking Adults
C11
275 משפטים
Every Networking Concept Explained In 20 Minutes
Daily ConversationUniversity StudentsWorking Adults
C11
180 משפטים
Armchair Architects: Resiliency in the Cloud – Core Patterns
Daily ConversationUniversity StudentsWorking Adults
C11
65 משפטים
Did Anthropic Kill Git?
Daily ConversationUniversity StudentsWorking Adults
C11
218 משפטים
Next.js 16.3 got good (if you care)
Daily ConversationWorking Adults
C11
40 משפטים
The Engineering that Runs the Digital World 🛠️⚙️💻 How do CPUs Work?
Daily ConversationUniversity StudentsWorking Adults
C11
132 משפטים
Helpdesk to Sysadmin - 3 Things You Must Learn First
Daily ConversationUniversity StudentsWorking Adults
C1231 משפטים
Redis Crash Course - the What, Why and How to use Redis as your primary database
Daily ConversationUniversity StudentsWorking Adults
אוצר מילים והערות הגייה לשיעור הזה
שיעור הדיבור הזה ברמה C1 מבוסס על הסרטון “I Bet Nobody Has Ever Explained the Backend Ecosystem Like This Before”. המילים שחוזרות הכי הרבה: application, backend, request, database, container. בסרטון הזה יש 164 משפטים ו-1878 מילים לתרגול Shadowing. הדיבור נמשך 12:41. הדובר שומר על קצב יציב של כ-148 מילים בדקה, קצב נוח לתרגול Shadowing. רק 77% מהמילים נמצאות בין 3,000 המילים הנפוצות ביותר באנגלית, כך שאוצר המילים מאתגר.
אוצר מילים מרכזי בסרטון הזה
15 המילים המתקדמות ביותר בסרטון, עם ההגייה והמשמעות שלהן:
| מילה | הגייה | משמעות |
|---|---|---|
| container שם עצם | /kənˈteɪ.nəɹ/ | מיכל |
| queue שם עצם | /kju/ | תּוֹר |
| cache שם עצם | /kæʃ/ | מִצְבּוֹר, מַחְבּוֹא |
| verify פועל | /ˈvɛɹɪfaɪ/ | וידא |
| proxy שם עצם | /ˈpɹɑk.si/ | שָׁלִיחַ |
| memorize פועל | /ˈmɛm.əˌɹaɪ̯z/ | שִׁנֵּן |
| metric שם תואר | /ˈmɛt.ɹɪk/ | מֶטְרִי |
| cart שם עצם | /kɑɹt/ | עֲגָלָה |
| dashboard שם עצם | /ˈdæʃˌboɹd/ | לוח מחוונים |
| behave פועל | /bɪˈheɪv/ | הִתְנַהֵג |
| subscribe פועל | /səbˈskɹaɪb/ | נִמְנָה |
| detect פועל | /dɪˈtɛkt/ | גילה, זיהה |
| warehouse שם עצם | /ˈwɛə(ɹ)haʊs/ | מַחְסָן |
| confirmation שם עצם | /ˌkɑn.fəɹˈmeɪ.ʃən/ | אִשּׁוּר \ אישור |
| approve פועל | /əˈpɹuːv/ | אִשֵּׁר |
Phrasal verbs שתשמעו
| מילה | משמעות |
|---|---|
| pick up פועל | הרים, אסף |
דקדוק בסרטון הזה
המבנים שהדובר משתמש בהם הכי הרבה, עם המילים המדויקות מהסרטון:
| מבנה | בסרטון |
|---|---|
| הווה מושלם ממושך (Present perfect continuous) have/has been + -ing — פעולה שהתחילה בעבר ועדיין נמשכת עכשיו | we've been following · I've already been covering |
| סביל (Passive voice) be + past participle — הדגש הוא על מה שקורה, לא על מי שעושה את הפעולה | may be forwarded · is called · is verified |
| הווה מושלם (Present perfect) have/has + past participle — פעולה שקרתה בעבר ועדיין יש לה חשיבות או השפעה עכשיו | you've ever searched · has now reached · has successfully saved |
הגייה ששווה לשים לב אליה
הדובר משתמש ב-19 קיצורים וצורות מקוצרות, כמו don't, they're, you've. אמרו אותם בצורה הקצרה, כפי שאתם שומעים אותם.
- הצלילים של “th”: authentication /ɔːˌθɛntɪˈkeɪʃn̩/, smoothly /ˈsmuːðli/
- הצלילים של “sh” ו-“zh”: cache /kæʃ/, authentication /ɔːˌθɛntɪˈkeɪʃn̩/, dashboard /ˈdæʃˌboɹd/, visualize /ˈvɪʒuəˌlaɪz/, unusually /ʌnˈjuːʒuəli/
- מילים ארוכות — שימו לב להטעמה: authentication /ɔːˌθɛntɪˈkeɪʃn̩/, manually /ˈmænj(u)əliː/, continuously /kənˈtɪnjuəsli/, analytic /ˌænəˈlɪtɪk/, repetitive /ɹɪˈpɛtɪtɪv/
צלילים שדוברי עברית מתקשים בהם:
- /w/ — שפתיים מעוגלות, לא /v/: overwhelm /ˌoʊ.vɚˈwɛlm/, query /ˈkwɪɹ.i/, warehouse /ˈwɛə(ɹ)haʊs/
- /æ/ — פתוח יותר מה-“אֶ” העברית, לא כמו “a” ב-“cup”: cache /kæʃ/, manually /ˈmænj(u)əliː/, analytic /ˌænəˈlɪtɪk/, dashboard /ˈdæʃˌboɹd/, interact /ɪn.təˈɹækt/
- /r/ — הלשון לא נוגעת בשום מקום, לא ה-“ר” הגרונית: container /kənˈteɪ.nəɹ/, verify /ˈvɛɹɪfaɪ/, proxy /ˈpɹɑk.si/, memorize /ˈmɛm.əˌɹaɪ̯z/, retrieve /ɹɪˈtɹiːv/
איך לתרגל עם הסרטון הזה
- הקשיבו לכל הסרטון פעם אחת בלי לדבר, ורשמו את המילים שאתם לא מכירים.
- תרגלו Shadowing משפט אחר משפט במהירות רגילה, וחזרו על כל משפט עד שהקצב שלכם תואם את הדובר.
- הקליטו את עצמכם והשוו למקור, תוך תשומת לב למילים כמו container, queue, cache.
מהי טכניקת השאדואינג?
שאדואינג היא טכניקת למידת שפה מבוססת מדע שפותחה במקור להכשרת מתורגמנים מקצועיים ופופולרית על ידי הפוליגלוט ד"ר אלכסנדר ארגואלס. השיטה פשוטה אך עוצמתית: אתה מקשיב לאודיו באנגלית ילידית וחוזר עליו בקול רם מיד — כמו צל העוקב אחרי הדובר עם עיכוב של 1–2 שניות בלבד. בניגוד להאזנה פסיבית או תרגילי דקדוק, שאדואינג מכריח את המוח והשרירים בפה לעבד ולשחזר דפוסי דיבור אמיתיים בו זמנית. מחקרים מראים שזה משפר משמעותית את דיוק ההגייה, האינטונציה, הקצב, הדיבור המחובר, הבנת השמיעה ושטף הדיבור — מה שהופך אותו לאחת השיטות היעילות ביותר להכנה לIELTS Speaking ולתקשורת באנגלית בעולם האמיתי.