शैडोइंग अभ्यास: Cache Systems Every Developer Should Know - वीडियो के साथ अंग्रेजी बोलना सीखें

पाठ बनाया जा रहा है...
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
📺 उसी चैनल से
The Secret Sauce Behind NoSQL: LSM TreeC1
1

The Secret Sauce Behind NoSQL: LSM Tree

Daily ConversationUniversity StudentsWorking Adults
Proxy vs Reverse Proxy (Real-world Examples)C1
3

Proxy vs Reverse Proxy (Real-world Examples)

Daily ConversationUniversity StudentsWorking Adults
System Design Was HARD - Until You Knew the Trade-OffsC1
3

System Design Was HARD - Until You Knew the Trade-Offs

Daily ConversationUniversity StudentsWorking Adults
8 Most Important System Design Concepts You Should KnowC1
7

8 Most Important System Design Concepts You Should Know

Daily ConversationUniversity StudentsWorking Adults
Everything You Need to Know About DNS: Crash Course System Design #4C1
3

Everything You Need to Know About DNS: Crash Course System Design #4

Daily ConversationUniversity StudentsWorking Adults
CAP Theorem SimplifiedC1
2

CAP Theorem Simplified

Daily ConversationUniversity StudentsWorking Adults
What Is REST API? Examples And How To Use It: Crash Course System Design #3C1
2

What Is REST API? Examples And How To Use It: Crash Course System Design #3

Daily ConversationUniversity StudentsWorking Adults
System Design: Why is Kafka Popular?C1
2

System Design: Why is Kafka Popular?

Business EnglishUniversity StudentsWorking Adults
What Are Microservices Really All About? (And When Not To Use It)C1
5

What Are Microservices Really All About? (And When Not To Use It)

Business EnglishUniversity StudentsWorking Adults
System Design: Why is Kafka fast?C1
1

System Design: Why is Kafka fast?

Business EnglishUniversity StudentsWorking Adults
What is API Gateway?C1
3

What is API Gateway?

Business EnglishUniversity StudentsWorking Adults
10+ Key Memory & Storage Systems: Crash Course System Design #5C1
2

10+ Key Memory & Storage Systems: Crash Course System Design #5

University StudentsWorking Adults
What Is Redis Really About? Why Is It So Popular?C2
4

What Is Redis Really About? Why Is It So Popular?

Business EnglishUniversity StudentsWorking Adults
Kubernetes Explained in 6 Minutes | k8s ArchitectureC1
48

Kubernetes Explained in 6 Minutes | k8s Architecture

Business EnglishUniversity StudentsWorking Adults
How Does a URL Shortener Work?C1
3

How Does a URL Shortener Work?

Business EnglishInterview EnglishUniversity Students
How Git Works: Explained in 4 MinutesB2

How Git Works: Explained in 4 Minutes

Business EnglishUniversity StudentsWorking Adults
✨ अनुशंसित वीडियो
Why Memory Prices Are Crazy HighC1
2
283 वाक्य

Why Memory Prices Are Crazy High

Daily ConversationUniversity StudentsWorking Adults
The Engineering that Runs the Digital World 🛠️⚙️💻 How do CPUs Work?C1
1
40 वाक्य

The Engineering that Runs the Digital World 🛠️⚙️💻 How do CPUs Work?

Daily ConversationUniversity StudentsWorking Adults
You are wasting memoryC1
1
27 वाक्य

You are wasting memory

Daily ConversationUniversity StudentsWorking Adults
What is Docker? Docker container concept explained || Docker Tutorial 1C1
2
102 वाक्य

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

Daily ConversationUniversity StudentsWorking Adults
Linus Torvalds Explains What Makes Linux So FastC1
32 वाक्य

Linus Torvalds Explains What Makes Linux So Fast

Daily ConversationUniversity StudentsWorking Adults
Armchair Architects: Resiliency in the Cloud – Core PatternsC1
1
180 वाक्य

Armchair Architects: Resiliency in the Cloud – Core Patterns

Daily ConversationUniversity StudentsWorking Adults
Amazon Athena explained in 120 seconds💡C1
15
29 वाक्य

Amazon Athena explained in 120 seconds💡

Daily ConversationUniversity StudentsWorking Adults
Usability Heuristic 2: Match Between the System and the Real WorldC1
3
31 वाक्य

Usability Heuristic 2: Match Between the System and the Real World

Daily ConversationUniversity StudentsWorking Adults
LangChain in 5 Minutes (Explained Clearly)C1
1
74 वाक्य

LangChain in 5 Minutes (Explained Clearly)

Daily ConversationUniversity StudentsWorking Adults
what is a database index?C1
3
68 वाक्य

what is a database index?

Daily ConversationUniversity StudentsWorking Adults

इस पाठ की शब्दावली और बोलने के सुझाव

यह स्पीकिंग पाठ वीडियो “Cache Systems Every Developer Should Know” पर आधारित है। सबसे ज़्यादा दोहराए गए शब्द ये हैं: cache, caching, memory, content, request। इस वीडियो में शैडोइंग के लिए 53 वाक्य और 802 शब्द हैं। बोला गया हिस्सा 5:37 लंबा है। वक्ता लगभग 143 शब्द प्रति मिनट की स्थिर गति से बोलता है, जो शैडोइंग के लिए आरामदायक है। केवल 75% शब्द अंग्रेज़ी के 3,000 सबसे आम शब्दों में से हैं, इसलिए शब्दावली कठिन है।

इस वीडियो की मुख्य शब्दावली

वीडियो के 15 सीखने लायक शब्द, उच्चारण और अर्थ के साथ:

शब्दउच्चारणअर्थ
server संज्ञा/ˈsɝvɚ/सर्वर
disk संज्ञा/dɪsk/डिस्क, चक्र
database संज्ञा/ˈdeɪtəˌbeɪs/डेटाबेस
architecture संज्ञा/ˈɑː.kɪˌtɛk.t͡ʃə/वास्तुकला, स्थापत्य
layer संज्ञा/ˈleɪ̯ɚ/परत, तह
hardware संज्ञा/ˈhɑɹdˌwɛɹ/हार्डवेयर
technique संज्ञा/tɛkˈniːk/तकनीक
topic संज्ञा/ˈtɑpɪk/प्रसंग, विषय
infrastructure संज्ञा/ˈɪnfɹəˌstɹʌkt͡ʃə/अवसंरचना
compare क्रिया/kəmˈpɛɚ/तौलना
resource संज्ञा/ɹɪˈzɔːs/संसाधन
translation संज्ञा/tɹænzˈleɪʃən/अनुवाद, भाषांतर
reader संज्ञा/ˈɹi.dɚ/पाठक, पाठिका
crucial विशेषण/ˈkɹuː.ʃəl/निर्णायक
mechanism संज्ञा/ˈmɛk.ə.nɪ.zəm/तंत्र, यंत्रावली

ध्यान देने योग्य उच्चारण

  • “sh” और “zh” की ध्वनियाँ: cache /kæʃ/, efficiency /ɪˈfɪʃ.ən.si/, transaction /tɹænˈzækʃən/, efficient /ɪˈfɪʃənt/, translation /tɹænzˈleɪʃən/
  • लंबे शब्द — बलाघात सही रखें: architecture /ˈɑː.kɪˌtɛk.t͡ʃə/, efficiency /ɪˈfɪʃ.ən.si/, infrastructure /ˈɪnfɹəˌstɹʌkt͡ʃə/, mechanism /ˈmɛk.ə.nɪ.zəm/, eliminate /ɪˈlɪm.ɪ.neɪt/

हिंदी भाषियों के लिए मुश्किल ध्वनियाँ:

  • /v/ और /w/ का फ़र्क़ — /v/ में ऊपर के दाँत निचले होंठ को छूते हैं, /w/ में होंठ गोल होते हैं: server /ˈsɝvɚ/, hardware /ˈhɑɹdˌwɛɹ/, virtual /ˈvɜɹt͡ʃuəl/, retrieve /ɹɪˈtɹiːv/, query /ˈkwɪɹ.i/
  • /z/ — इसे “ज” (/dʒ/) न बनाएँ: transaction /tɹænˈzækʃən/, browser /ˈbɹaʊ.zəɹ/, zoom /zuːm/, resource /ɹɪˈzɔːs/, translation /tɹænzˈleɪʃən/
  • /æ/ — “ऐ” से ज़्यादा खुला: cache /kæʃ/, transaction /tɹænˈzækʃən/, translation /tɹænzˈleɪʃən/, static /ˈstæt.ɪk/, enhance /ɪnˈhæns/

इस वीडियो से अभ्यास कैसे करें

  1. पहले बिना बोले पूरा वीडियो एक बार सुनें और जो शब्द नहीं आते उन्हें लिख लें।
  2. सामान्य गति पर एक-एक वाक्य की शैडोइंग करें और हर वाक्य तब तक दोहराएँ जब तक आपकी लय वक्ता से न मिल जाए।
  3. अपनी आवाज़ रिकॉर्ड करें और मूल से तुलना करें, ख़ासकर server, disk, database जैसे शब्दों पर ध्यान दें।

शैडोइंग तकनीक क्या है?

शैडोइंग (Shadowing) एक विज्ञान-समर्थित भाषा सीखने की तकनीक है जो मूल रूप से पेशेवर दुभाषिया प्रशिक्षण के लिए विकसित की गई थी। विधि सरल लेकिन शक्तिशाली है: आप मूल अंग्रेज़ी ऑडियो सुनते हैं और तुरंत इसे ज़ोर से दोहराते हैं — जैसे वक्ता की छाया 1-2 सेकंड की देरी से। शोध से पता चलता है कि यह उच्चारण सटीकता, स्वर, लय, जुड़ी हुई ध्वनियाँ, सुनने की समझ और बोलने की प्रवाहशीलता में काफ़ी सुधार करता है।

शैडोइंग तकनीक: पूरी चरण-दर-चरण गाइड पढ़ें →