Shadowing-Übung: Cache Systems Every Developer Should Know - Englisch Sprechen Lernen mit Video
Übungsmodus wählen
Jeder Modus öffnet einen Übungsraum im Vollbild.
53 Sätze
Wenn Sätze zu kurz oder zu lang sind, klicke auf Edit, um sie anzupassen.
1
Caching is a common technique in modern computing to enhance system performance and reduce response time.
2
From the front end to the back end, caching plays a crucial role in improving the efficiency of various applications and systems.
3
A typical system architecture involves several layers of caching.
4
At each layer, there are multiple strategies and mechanisms for caching data, depending on the requirements and the constraints of the specific application.
5
Before diving into a typical system architecture, let's zoom in and look at how prevalent caching is within each computer itself.
6
Let's first look at the computer hardware.
7
The most common hardware caches are L1, L2, and L3 caches.
8
L1 cache is the smallest and fastest cache, typically integrated into the CPU itself.
9
It stores frequently accessed data and instructions, allowing the CPU to quickly access them without having to fetch them from slower memory.
10
L2 cache is larger but slower than L1 cache, and is typically located on the CPU die.
11
L3 cache is even larger and slower than L2 cache, and is often shared between multiple CPU cores.
12
Another common hardware cache is the Translation Look -Aside Buffer, or TLB.
13
It stores recently used virtual to physical address translations.
14
It is used by the CPU to quickly translate virtual memory addresses to physical memory addresses, reducing the time needed to access data from memory.
15
At the operating system level, there are PageCache and other file system caches.
16
PageCache is managed by the operating system and resides in main memory.
17
It is used to store recently used disk blocks in memory.
18
When a program requests data from the disk, the operating system can quickly retrieve the data from memory instead of reading it from disk.
19
There are other caches managed by the operating system such as the iNode cache.
20
These caches are used to speed up file system operations by
21
reducing the number of disk accesses required to access files and directories.
22
Now let's zoom out and look at how caching is used in a typical application system architecture.
23
On the application front end, web browsers can cache HTTP responses to enable faster retrieval of data.
24
When we request data over HTTP for the first time and it is returned with an expiration policy in the HTTP header.
25
We request the same data again, and the browser returns the data from its cache if available.
26
Content delivery network, or CDNs, are widely used to improve the delivery of static content,
27
such as images, videos, and other web access.
28
One of the ways that CDNs speed up content delivery is through caching.
29
When a user requests contents from a CDN, the CDN network looks for the requested content in its cache.
30
If the content is not already in the cache, the CDN fetches it from the origin server and caches it on its edge servers.
31
When another user requests the same content, the CDN can deliver the content directly from its cache,
32
eliminating the need to fetch it from the origin server again.
33
Some load balancers can cache resources to reduce the load on back -end servers.
34
When a user requests content from a server behind a load balancer,
35
the load balancer can cache the response and serve it directly to future users who request the same content.
36
This can improve response times and reduce the load on back -end servers.
37
Caching does not always have to be in memory.
38
In messaging infrastructure, message brokers such as Kafka can cache a massive amount of messages on disk.
39
This allows consumers to retrieve the messages at their own pace.
40
The messages can be cached for a long period of time based on the retention policy.
41
Distributed caches such as Redis can store key value pairs in memory, providing high read -write performance compared to traditional databases.
42
Full text search engines, such as Elasticsearch, can index data for document search and log search,
43
providing quick and efficient access to specific data.
44
Even within the database, there are multiple levels of caching available.
45
Data is typically written to a write -ahead log before being indexed in a B -tree.
46
The buffer pool is a memory area used to cache query results, while materialized views can pre -compute query results for faster performance.
47
The transaction log records all transactions and updates to the database, while the replication log tracks the replication state in a database cluster.
48
Overall, caching data is an essential technique for optimizing system performance and reducing response time.
49
From the front end to the back end, there are many layers of caching to improve the efficiency of various applications and systems.
50
If you like our videos, you might like our system design newsletter as well.
51
It covers topics and trends in large -scale system design.
52
Trusted by 300 ,000 readers.
53
Subscribe at blog .bitebygo .com
App herunterladen
Alles, was du zum fließenden Sprechen brauchst
KI-AussprachebewertungJeder Satz bewertet
IPA-TrainingJeden Laut meistern
WortschatzBaue deinen Wortschatz auf
VokabelspielSpielend lernen
📺 Gleicher Kanal
C11
The Secret Sauce Behind NoSQL: LSM Tree
Daily ConversationUniversity StudentsWorking Adults
C13
Proxy vs Reverse Proxy (Real-world Examples)
Daily ConversationUniversity StudentsWorking Adults
C13
System Design Was HARD - Until You Knew the Trade-Offs
Daily ConversationUniversity StudentsWorking Adults
C17
8 Most Important System Design Concepts You Should Know
Daily ConversationUniversity StudentsWorking Adults
C13
Everything You Need to Know About DNS: Crash Course System Design #4
Daily ConversationUniversity StudentsWorking Adults
C12
CAP Theorem Simplified
Daily ConversationUniversity StudentsWorking Adults
C12
What Is REST API? Examples And How To Use It: Crash Course System Design #3
Daily ConversationUniversity StudentsWorking Adults
C12
System Design: Why is Kafka Popular?
Business EnglishUniversity StudentsWorking Adults
C15
What Are Microservices Really All About? (And When Not To Use It)
Business EnglishUniversity StudentsWorking Adults
C11
System Design: Why is Kafka fast?
Business EnglishUniversity StudentsWorking Adults
C13
What is API Gateway?
Business EnglishUniversity StudentsWorking Adults
C12
10+ Key Memory & Storage Systems: Crash Course System Design #5
University StudentsWorking Adults
C24
What Is Redis Really About? Why Is It So Popular?
Business EnglishUniversity StudentsWorking Adults
C148
Kubernetes Explained in 6 Minutes | k8s Architecture
Business EnglishUniversity StudentsWorking Adults
C13
How Does a URL Shortener Work?
Business EnglishInterview EnglishUniversity Students
B2How Git Works: Explained in 4 Minutes
Business EnglishUniversity StudentsWorking Adults
✨ Empfohlenes Video
C12
283 Sätze
Why Memory Prices Are Crazy High
Daily ConversationUniversity StudentsWorking Adults
C11
40 Sätze
The Engineering that Runs the Digital World 🛠️⚙️💻 How do CPUs Work?
Daily ConversationUniversity StudentsWorking Adults
C11
27 Sätze
You are wasting memory
Daily ConversationUniversity StudentsWorking Adults
C12
102 Sätze
What is Docker? Docker container concept explained || Docker Tutorial 1
Daily ConversationUniversity StudentsWorking Adults
C132 Sätze
Linus Torvalds Explains What Makes Linux So Fast
Daily ConversationUniversity StudentsWorking Adults
C11
180 Sätze
Armchair Architects: Resiliency in the Cloud – Core Patterns
Daily ConversationUniversity StudentsWorking Adults
C115
29 Sätze
Amazon Athena explained in 120 seconds💡
Daily ConversationUniversity StudentsWorking Adults
C13
31 Sätze
Usability Heuristic 2: Match Between the System and the Real World
Daily ConversationUniversity StudentsWorking Adults
C11
74 Sätze
LangChain in 5 Minutes (Explained Clearly)
Daily ConversationUniversity StudentsWorking Adults
C13
68 Sätze
what is a database index?
Daily ConversationUniversity StudentsWorking Adults
Wortschatz und Sprechhinweise zu dieser Lektion
Diese Sprechübung basiert auf dem Video „Cache Systems Every Developer Should Know“. Diese Wörter kommen am häufigsten vor: cache, caching, memory, content, request. Dieses Video enthält 53 Sätze und 802 Wörter zum Nachsprechen. Der gesprochene Teil dauert 5:37. Der Sprecher spricht gleichmäßig mit etwa 143 Wörtern pro Minute – ein angenehmes Tempo fürs Shadowing. Nur 75 % der Wörter gehören zu den 3.000 häufigsten im Englischen, der Wortschatz ist also anspruchsvoll.
Wichtiger Wortschatz in diesem Video
15 lernenswerte Wörter aus dem Video, mit Aussprache und Bedeutung:
| Wort | Aussprache | Bedeutung |
|---|---|---|
| cache Substantiv | /kæʃ/ | Cache, Zwischenspeicher |
| server Substantiv | /ˈsɝvɚ/ | Server |
| disk Substantiv | /dɪsk/ | Scheibe, Kreisscheibe |
| database Substantiv | /ˈdeɪtəˌbeɪs/ | Datenbank |
| architecture Substantiv | /ˈɑː.kɪˌtɛk.t͡ʃə/ | Architektur, Baustil |
| layer Substantiv | /ˈleɪ̯ɚ/ | Lage, Schicht |
| hardware Substantiv | /ˈhɑɹdˌwɛɹ/ | Eisenwaren |
| fetch Verb | /fɛt͡ʃ/ | holen |
| technique Substantiv | /tɛkˈniːk/ | Technik |
| efficiency Substantiv | /ɪˈfɪʃ.ən.si/ | Effizienz, Leistungsfähigkeit |
| virtual Adjektiv | /ˈvɜɹt͡ʃuəl/ | virtuell, eigentlich |
| transaction Substantiv | /tɹænˈzækʃən/ | Geschäftsabwicklung, Geschäftsdurchführung |
| zoom Verb | /zuːm/ | schwirren, surren |
| buffer Substantiv | /ˈbʌfəɹ/ | Puffer |
| retrieve Verb | /ɹɪˈtɹiːv/ | zurückholen, zurückerhalten |
Phrasal Verbs, die du hören wirst
| Wort | Aussprache | Bedeutung |
|---|---|---|
| speed up Verb | /spiːdˈʌp/ | beschleunigen |
Aussprache, auf die du achten solltest
- Die Laute „sh“ und „zh“: cache /kæʃ/, efficiency /ɪˈfɪʃ.ən.si/, transaction /tɹænˈzækʃən/, efficient /ɪˈfɪʃənt/, translation /tɹænzˈleɪʃən/
- Lange Wörter – auf die Betonung achten: architecture /ˈɑː.kɪˌtɛk.t͡ʃə/, efficiency /ɪˈfɪʃ.ən.si/, infrastructure /ˈɪnfɹəˌstɹʌkt͡ʃə/, mechanism /ˈmɛk.ə.nɪ.zəm/, eliminate /ɪˈlɪm.ɪ.neɪt/
Laute, die Deutschsprachigen schwerfallen:
- /w/ — mit runden Lippen, nicht wie das deutsche „w“ (/v/): hardware /ˈhɑɹdˌwɛɹ/, query /ˈkwɪɹ.i/, requirement /ɹɪˈkwaɪɹmənt/
- Stimmhafter Auslaut — /b/, /d/, /g/, /z/, /v/ am Wortende nicht verhärten: retrieve /ɹɪˈtɹiːv/, involve /ɪnˈvɑlv/, depend /dɪˈpɛnd/, dive /daɪv/, subscribe /səbˈskɹaɪb/
- /æ/ — offener als „ä“: cache /kæʃ/, transaction /tɹænˈzækʃən/, translation /tɹænzˈleɪʃən/, static /ˈstæt.ɪk/, enhance /ɪnˈhæns/
So übst du mit diesem Video
- Höre dir das ganze Video einmal an, ohne zu sprechen, und notiere die Wörter, die du nicht kennst.
- Sprich Satz für Satz in normaler Geschwindigkeit nach und wiederhole jeden, bis dein Rhythmus zum Sprecher passt.
- Nimm dich auf und vergleiche mit dem Original; achte dabei auf Wörter wie cache, server, disk.
Was ist die Shadowing-Technik?
Shadowing ist eine wissenschaftlich fundierte Sprachlerntechnik, die ursprünglich für die professionelle Dolmetscherausbildung entwickelt und durch den Polyglotten Dr. Alexander Arguelles populär gemacht wurde. Die Methode ist einfach aber wirkungsvoll: Du hörst englisches Audio von Muttersprachlern und wiederholst es sofort laut — wie ein Schatten, der dem Sprecher mit nur 1–2 Sekunden Verzögerung folgt. Anders als passives Hören oder Grammatikübungen zwingt Shadowing dein Gehirn und deine Mundmuskulatur, gleichzeitig echte Sprachmuster zu verarbeiten und zu reproduzieren. Studien zeigen, dass es Aussprachegenauigkeit, Intonation, Rhythmus, verbundene Sprache, Hörverständnis und Sprechflüssigkeit signifikant verbessert — was es zu einer der effektivsten Methoden für die IELTS Speaking-Vorbereitung und reale englische Kommunikation macht.