シャドーイング練習: Cache Systems Every Developer Should Know - 動画で英語スピーキングを学ぶ
練習モードを選ぶ
各モードは全画面の練習ルームで開きます。
53 文
文が短すぎたり長すぎる場合は、Editをタップして調整してください。
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
アプリをダウンロード
流暢に話すために必要なすべて
AI発音採点文ごとに採点
IPA練習すべての音をマスター
単語学習自分の単語帳を作る
単語ゲーム遊びながら覚える
📺 同じチャンネル
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
C11
System Design: Why is Kafka fast?
Business EnglishUniversity StudentsWorking Adults
C16
What Are Microservices Really All About? (And When Not To Use It)
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
✨ おすすめ動画
C12
283 文
Why Memory Prices Are Crazy High
Daily ConversationUniversity StudentsWorking Adults
C11
40 文
The Engineering that Runs the Digital World 🛠️⚙️💻 How do CPUs Work?
Daily ConversationUniversity StudentsWorking Adults
C11
27 文
You are wasting memory
Daily ConversationUniversity StudentsWorking Adults
C12
102 文
What is Docker? Docker container concept explained || Docker Tutorial 1
Daily ConversationUniversity StudentsWorking Adults
C132 文
Linus Torvalds Explains What Makes Linux So Fast
Daily ConversationUniversity StudentsWorking Adults
C11
180 文
Armchair Architects: Resiliency in the Cloud – Core Patterns
Daily ConversationUniversity StudentsWorking Adults
C115
29 文
Amazon Athena explained in 120 seconds💡
Daily ConversationUniversity StudentsWorking Adults
C13
31 文
Usability Heuristic 2: Match Between the System and the Real World
Daily ConversationUniversity StudentsWorking Adults
C11
74 文
LangChain in 5 Minutes (Explained Clearly)
Daily ConversationUniversity StudentsWorking Adults
C13
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です。 話す速さは1分あたり約143語で安定しており、シャドーイングしやすいペースです。 英語の頻出3,000語に含まれる単語は75%だけなので、語彙は難しめです。
この動画の重要語彙
動画に出てくる覚えておきたい単語15語を、発音と意味つきで紹介します。
| 単語 | 発音 | 意味 |
|---|---|---|
| cache 名詞 | /kæʃ/ | キャッシュ |
| server 名詞 | /ˈsɝvɚ/ | サーバー |
| disk 名詞 | /dɪsk/ | ディスク, 円盤 |
| database 名詞 | /ˈdeɪtəˌbeɪs/ | データベース |
| architecture 名詞 | /ˈɑː.kɪˌtɛk.t͡ʃə/ | 建築, 建築学 |
| layer 名詞 | /ˈleɪ̯ɚ/ | 層, 膜 |
| hardware 名詞 | /ˈhɑɹdˌwɛɹ/ | ハードウェア, ハード |
| fetch 動詞 | /fɛt͡ʃ/ | 持ち帰る |
| technique 名詞 | /tɛkˈniːk/ | 技術 |
| efficiency 名詞 | /ɪˈfɪʃ.ən.si/ | 効率性, 効率 |
| virtual 形容詞 | /ˈvɜɹt͡ʃuəl/ | 事実上の |
| transaction 名詞 | /tɹænˈzækʃən/ | 処理 |
| zoom 動詞 | /zuːm/ | 猛スピードで進む |
| retrieve 動詞 | /ɹɪˈtɹiːv/ | 取り戻す |
| query 名詞 | /ˈkwɪɹ.i/ | 質問 |
動画に出てくる句動詞
| 単語 | 発音 | 意味 |
|---|---|---|
| speed up 動詞 | /spiːdˈʌp/ | スピードを出す |
| zoom out 動詞 | /ˌzuːm ˈaʊt/ | ズームアウトする, 縮小する |
注意したい発音
- 「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/
日本語話者が苦手な音：
- /r/ と /l/ の区別 — /l/ は舌先を歯茎につけ、/r/ はどこにもつけない: virtual /ˈvɜɹt͡ʃuəl/, translation /tɹænzˈleɪʃən/, crucial /ˈkɹuː.ʃəl/, translate /tɹænzˈleɪt/, prevalent /ˈpɹɛvələnt/
- /v/ — /b/ にならないように、上の歯を下唇に当てる: server /ˈsɝvɚ/, virtual /ˈvɜɹt͡ʃuəl/, retrieve /ɹɪˈtɹiːv/, involve /ɪnˈvɑlv/, dive /daɪv/
- /f/ — 「フ」ではなく、上の歯と下唇で出す: fetch /fɛt͡ʃ/, efficiency /ɪˈfɪʃ.ən.si/, buffer /ˈbʌfəɹ/, infrastructure /ˈɪnfɹəˌstɹʌkt͡ʃə/, efficient /ɪˈfɪʃənt/
この動画での練習方法
- まず声を出さずに動画を最後まで聞き、知らない単語をメモします。
- 通常の速度で一文ずつシャドーイングし、話し手のリズムに合うまで繰り返します。
- 自分の声を録音して元の音声と比べます。cache, server, diskなどの単語に特に注意しましょう。
シャドーイングとは？英語上達に効果的な理由
シャドーイング（Shadowing）は、もともとプロの通訳者養成プログラムで開発された言語学習法で、多言語習得者として知られるDr. Alexander Arguelles によって広く普及されました。方法はシンプルですが非常に効果的：ネイティブスピーカーの英語を聞きながら、1〜2秒の遅延で声に出してすぐに繰り返す——まるで「影（shadow）」のように話者を追いかけます。文法ドリルや受動的なリスニングと異なり、シャドーイングは脳と口の筋肉が同時にリアルタイムで英語を処理・再現することを強制します。研究により、発音精度、抑揚、リズム、連音、リスニング力、そして会話の流暢さが大幅に向上することが確認されています。IELTSスピーキング対策や自然な英語コミュニケーションを目指す方に特におすすめです。