Shadowing Practice: Cache Systems Every Developer Should Know - Learn English Speaking with Video
Ders oluşturuluyor...
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
📺 Aynı 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
Business EnglishUniversity StudentsWorking Adults
C17
8 Most Important System Design Concepts You Should Know
Business EnglishUniversity StudentsWorking Adults
C13
Everything You Need to Know About DNS: Crash Course System Design #4
Business EnglishUniversity StudentsWorking Adults
C12
CAP Theorem Simplified
Business EnglishUniversity StudentsWorking Adults
C12
What Is REST API? Examples And How To Use It: Crash Course System Design #3
Business EnglishUniversity StudentsWorking Adults
C12
System Design: Why is Kafka Popular?
Business EnglishUniversity StudentsWorking Adults
C12
What is API Gateway?
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
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
✨ Video Öner
C12
283 cümleler
Why Memory Prices Are Crazy High
Daily ConversationUniversity StudentsWorking Adults
C132 cümleler
Linus Torvalds Explains What Makes Linux So Fast
Daily ConversationUniversity StudentsWorking Adults
C11
126 cümleler
Therapy for the Vibe-Coded Brain
Daily ConversationUniversity StudentsWorking Adults
B21
375 cümleler
Configure storage accounts | AZ-104 | Episode 16
Daily ConversationUniversity StudentsWorking Adults
C11
65 cümleler
How do microSD Cards Store 2 TB in such a TINY space?
Daily ConversationUniversity StudentsWorking Adults
B21
336 cümleler
Best NextJS Folder Structures | Beginner - Intermediate - Advanced
Daily ConversationUniversity StudentsWorking Adults
C11
114 cümleler
Design a File Upload Service Like a Senior Engineer
Daily ConversationUniversity StudentsWorking Adults
C11
128 cümleler
Demystifying MCP | Architect Insights
Daily ConversationWorking Adults
C11
27 cümleler
You are wasting memory
Business EnglishUniversity StudentsWorking Adults
B23
87 cümleler
Data Engineering - Practice English Conversation
Business EnglishDaily ConversationUniversity Students
Bu dersin kelimeleri ve konuşma notları
Bu konuşma dersi “Cache Systems Every Developer Should Know” videosuna dayanıyor. En çok tekrarlanan kelimeler: cache, caching, memory, content, request. Bu videoda gölgeleme çalışması için 53 cümle ve 802 kelime var. Konuşma bölümü 5:37 sürüyor. Konuşmacı dakikada yaklaşık 143 kelimelik dengeli bir hızla konuşuyor; gölgeleme için rahat bir tempo. Kelimelerin yalnızca %75’i İngilizcede en sık kullanılan 3.000 kelime arasında, bu yüzden kelime dağarcığı zorlayıcı.
Bu videodaki önemli kelimeler
Videodan öğrenmeye değer 15 kelime, telaffuzu ve anlamıyla:
| Kelime | Telaffuz | Anlam |
|---|---|---|
| cache isim | /kæʃ/ | önbellek |
| server isim | /ˈsɝvɚ/ | sunucu, server |
| disk isim | /dɪsk/ | disk, ağırşak |
| database isim | /ˈdeɪtəˌbeɪs/ | veritabanı, veri tabanı |
| architecture isim | /ˈɑː.kɪˌtɛk.t͡ʃə/ | mimarlık |
| layer isim | /ˈleɪ̯ɚ/ | katman, tabaka |
| hardware isim | /ˈhɑɹdˌwɛɹ/ | hırdavat |
| technique isim | /tɛkˈniːk/ | teknik |
| efficiency isim | /ɪˈfɪʃ.ən.si/ | verimlilik |
| virtual sıfat | /ˈvɜɹt͡ʃuəl/ | sanal |
| retrieve fiil | /ɹɪˈtɹiːv/ | geri almak |
| query isim | /ˈkwɪɹ.i/ | sorgulama |
| topic isim | /ˈtɑpɪk/ | mevzu, tema |
| infrastructure isim | /ˈɪnfɹəˌstɹʌkt͡ʃə/ | altyapı, enfrastrüktür |
| compare fiil | /kəmˈpɛɚ/ | karşılaştırmak, kıyaslamak |
Duyacağınız deyimsel fiiller
| Kelime | Telaffuz | Anlam |
|---|---|---|
| speed up fiil | /spiːdˈʌp/ | hızlanmak, hızlandırmak |
Bu videodaki dil bilgisi
Konuşmacının en çok kullandığı yapılar, videodaki sözcüklerin aynısıyla:
| Yapı | Videoda |
|---|---|
| “Used to” used to + fiil — artık geçerli olmayan eski bir alışkanlık ya da durum | used to improve · used to cache |
| Edilgen yapı be + fiilin üçüncü hâli — kimin yaptığı değil, ne olduğu önemli | is often shared · is managed · is returned |
Dikkat edilecek telaffuzlar
- “sh” ve “zh” sesleri: cache /kæʃ/, efficiency /ɪˈfɪʃ.ən.si/, transaction /tɹænˈzækʃən/, efficient /ɪˈfɪʃənt/, translation /tɹænzˈleɪʃən/
- Uzun kelimeler — vurguyu doğru yere koyun: architecture /ˈɑː.kɪˌtɛk.t͡ʃə/, efficiency /ɪˈfɪʃ.ən.si/, infrastructure /ˈɪnfɹəˌstɹʌkt͡ʃə/, mechanism /ˈmɛk.ə.nɪ.zəm/, eliminate /ɪˈlɪm.ɪ.neɪt/
Türkçe konuşanların zorlandığı sesler:
- /w/ — dudaklar yuvarlak, /v/ değil: hardware /ˈhɑɹdˌwɛɹ/, query /ˈkwɪɹ.i/, requirement /ɹɪˈkwaɪɹmənt/
- Kelime başındaki ünsüz kümesi — araya ünlü eklemeyin: transaction /tɹænˈzækʃən/, browser /ˈbɹaʊ.zəɹ/, query /ˈkwɪɹ.i/, translation /tɹænzˈleɪʃən/, crucial /ˈkɹuː.ʃəl/
- /æ/ — “e”den daha açık: cache /kæʃ/, transaction /tɹænˈzækʃən/, translation /tɹænzˈleɪʃən/, static /ˈstæt.ɪk/, enhance /ɪnˈhæns/
Bu videoyla nasıl çalışılır
- Videonun tamamını konuşmadan bir kez dinleyin ve bilmediğiniz kelimeleri not edin.
- Normal hızda cümle cümle tekrar edin; ritminiz konuşmacıyla aynı olana kadar her cümleyi yineleyin.
- Kendinizi kaydedin ve orijinaliyle karşılaştırın; cache, server, disk gibi kelimelere özellikle dikkat edin.
Gölgeleme Tekniği Nedir?
Gölgeleme, başlangıçta profesyonel tercüman eğitimi için geliştirilen ve çok dilli Dr. Alexander Arguelles tarafından popüler hale getirilen, bilim destekli bir dil öğrenme tekniğidir. Yöntem basit ama güçlüdür: ana dili İngilizce olan bir sesi dinler ve hemen yüksek sesle tekrar edersiniz — konuşmacıyı 1-2 saniye gecikmeyle takip eden bir gölge gibi. Pasif dinleme veya dilbilgisi alıştırmalarının aksine, gölgeleme beyninizi ve ağız kaslarınızı gerçek konuşma kalıplarını eşzamanlı olarak işlemeye ve yeniden üretmeye zorlar. Araştırmalar, telaffuz doğruluğu, tonlama, ritim, bağlı konuşma, dinleme anlama ve konuşma akıcılığını önemli ölçüde geliştirdiğini göstermektedir — bu da onu IELTS Konuşma hazırlığı ve gerçek dünya İngilizce iletişimi için en etkili yöntemlerden biri yapar.