シャドーイング練習: Top 5 Redis Use Cases - 動画で英語スピーキングを学ぶ

練習モードを選ぶ

各モードは全画面の練習ルームで開きます。

75 文

文が短すぎたり長すぎる場合は、Editをタップして調整してください。

In this video, we discover the versatility of Redis.

We'll talk about the top use cases that have been better tested in production at various companies and at various scales.

Get insights into how Redis solves interesting scalability challenges for us

and learn why it is a great tool to know well in our system design toolset.

Let's dive right into it.

First of all, what is Redis and why do people use it?

Redis is an in -memory data structure store.

It is most commonly used as a cache.

It supports many data structures such as strings, hashes, lists, sets, and sorted sets.

Redis is known for its speed.

We made a video to explain why Redis is so fast.

Look for the link in the description if you would like to watch that video.

Now let's dive into the top use cases of Redis.

The number one use case of Redis is caching objects to speed up web applications.

In this use case, Redis stores frequently requested data in memory.

It allows the web servers to return frequently accessed data quickly.

This reduces the load on the database and improves the response time for the application.

At scale, the cache is distributed among a cluster of Redis servers.

Sharding is a common technique to distribute and caching load evenly across the cluster.

Other topics to consider when deploying Redis as a distributed cache include setting a correct TTL

and handling thundering hurt on cold start.

Another common use case is to use Redis as a session store to share session data among stateless servers.

When a user logs into a web application, the session data is stored in Redis,

along with a unique session ID that is returned to the client as a cookie.

When a user makes a request to the application, the session ID is included in the request,

and the stateless web server retrieves the session data from Redis using the ID.

It is important to note that Redis is an in -memory database.

The session data stored in Redis will be lost if the Redis server restarts.

Even though Redis provides persistent options like a snapshot and AOF or append -only file,

they allow session data to be saved to disk and reloaded into memory in the event of a restart.

These options often take too long to load to be practical.

In production, replication is usually used instead.

In this case, data is replicated to a backup instance.

In the event of a crash of the main instance, the backup instance is quickly promoted to take over the traffic.

The next use case is distributed log.

Distributed logs are used when multiple nodes in an application need to coordinate access to some shared resource.

Redis is used as a distributed log with its atomic commands like set -nx or set -if -not -exists.

It allows a caller to set a key only if it does not already exist.

Here's how it works at a high level.

Client 1 tries to acquire the log by setting a key with a unique value

and a timeout using the set -nx command.

If the key was not already set, the set -nx command returns 1, indicating that the log has been acquired by client 1.

Client 1 finishes its work and releases the log by deleting the key.

Now if the key was already set, the set -annex command returns 0, indicating that the log has already been held by another client.

In this case, client 1 waits and retries the set -annex operation until the log is released by the other client.

Note that this simple implementation might be good enough for many use cases, but it is not completely fault -tolerant.

For production use, there are many Redis client libraries that provide high -quality distributed log implementation built right off the box.

Next up is Ray Limiter.

Redis can be used as a Ray Limiter by using its increment command on some counters

and setting expiration times on those counters.

A very basic

Ray Limiting algorithm works this way.

For each incoming request, the request IP or user ID is used as a key.

The number of requests for the key is incremented using the increment command in Redis.

The current count is compared to the allowed rate limit.

If the count is within the rate limit, the request is processed.

If the count is over the limit, the request is rejected.

The keys are set to expire after a specific time window, for example, a minute, to reset the cans for the next time window.

More sophisticated rate limiters, like the leaky bucket algorithm, can also be implemented using Redis.

The last use case we would like to talk about is gaming leaderboard.

For most games that are not super high scale, Redis is a delightful way to implement various types of gaming leaderboards.

Sort of sets are the fundamental data structure that enables this.

A sort of set is a collection of unique elements, each with a score associated with it.

The elements are sorted by score.

This allows for quick retrieval of the elements by score in logarithmic time.

That's it for our top Redis use cases.

Redis is very versatile.

There are many different ways to use it.

Some features are more better tested than others.

Our creativity is the limit.

Use it with care and have fun with it.

You would like our videos.

You may like our weekly system design newsletter as well.

It covers topics and trends in large -scale system design, trusted by 200 ,000 readers.

Subscribe at blog .buybygo .com.

アプリをダウンロード

流暢に話すために必要なすべて

AI発音採点文ごとに採点

IPA練習すべての音をマスター

単語学習自分の単語帳を作る

単語ゲーム遊びながら覚える

QRをスキャン

Download on theApp Store Get it onGoogle Play

同じチャンネル

FOR YOU

このレッスンの語彙とスピーキングのポイント

このスピーキングレッスンは、動画「Top 5 Redis Use Cases」を教材にしています。繰り返し出てくる語は次のとおりです：Redis, log, client, session, key。この動画には、シャドーイング用の文が75文、単語が937語あります。音声の長さは6:16です。話す速さは1分あたり約149語で安定しており、シャドーイングしやすいペースです。英語の頻出3,000語に含まれる単語は77%だけなので、語彙は難しめです。

この動画の重要語彙

動画に出てくる覚えておきたい単語15語を、発音と意味つきで紹介します。

単語	発音	意味
distribute 動詞	/dɪˈstɹɪbjuːt/	分ける
server 名詞	/ˈsɝvɚ/	サーバー
cache 名詞	/kæʃ/	キャッシュ
element 名詞	/ˈɛləmənt/	要素, エレメント
topic 名詞	/ˈtɑpɪk/	話題, テーマ
log 名詞	/lɔɡ/	丸太, 丸木
indicate 動詞	/ˈɪndɪˌkeɪt/	示す, 指す
database 名詞	/ˈdeɪtəˌbeɪs/	データベース
implementation 名詞	/ˌɪmplɪmənˈteɪʃən/	実施, 実用化
backup 名詞	/ˈbækˌʌp/	予備, 控え
implement 動詞	/ˈɪmpləmənt/	実行する, 実現する
acquire 動詞	/əˈkwaɪɚ/	獲得する
dive 動詞	/daɪv/	潜る
algorithm 名詞	/ˈælɡəɹɪðm̩/	アルゴリズム, 演算手順
annex 名詞	/əˈnɛks/	付加物, 付属

動画に出てくる句動詞

単語	発音	意味
speed up 動詞	/spiːdˈʌp/	スピードを出す
take over 動詞		引き受ける

この動画の文法

話し手がよく使っている文型を、動画の実際の表現とともに紹介します。

文型	動画での表現
受動態 be + 過去分詞 — 誰がするかより、何が起きるかに焦点を当てる	is known · is distributed · is stored
現在完了形 have/has + 過去分詞 — 過去の出来事が今も関係している	have been · has been acquired · has already been held

注意したい発音

「th」の音: algorithm /ˈælɡəɹɪðm̩/, thunder /ˈθʌndɚ/, logarithmic /ˌlɒɡəˈɹɪðmɪk/
「sh」と「zh」の音: cache /kæʃ/, implementation /ˌɪmplɪmənˈteɪʃən/, associate /əˈsoʊʃi.ət/, hash /ˈhæʃ/, expiration /ˌɛk.spɚˈeɪ̯.ʃən/
長い単語（アクセントの位置に注意）: implementation /ˌɪmplɪmənˈteɪʃən/, associate /əˈsoʊʃi.ət/, fundamental /ˌfʌn.dəˈmɛn.təl/, creativity /kri.eɪˈtɪv.ᵻ.ti/, coordinate /koʊˈɔɹ.dəˌneɪt/

日本語話者が苦手な音：

/r/ と /l/ の区別 — /l/ は舌先を歯茎につけ、/r/ はどこにもつけない: algorithm /ˈælɡəɹɪðm̩/, practical /ˈpɹæk.tɪ.kəl/, tolerant /ˈtɑːləɹənt/, replicate /ˈɹɛplɪkeɪt/, logarithmic /ˌlɒɡəˈɹɪðmɪk/
/v/ — /b/ にならないように、上の歯を下唇に当てる: server /ˈsɝvɚ/, dive /daɪv/, solve /sɒlv/, discover /dɪˈskʌvə/, creativity /kri.eɪˈtɪv.ᵻ.ti/
/f/ — 「フ」ではなく、上の歯と下唇で出す: fundamental /ˌfʌn.dəˈmɛn.təl/, delightful /dəˈlaɪt.fl̩/

この動画での練習方法

まず声を出さずに動画を最後まで聞き、知らない単語をメモします。
通常の速度で一文ずつシャドーイングし、話し手のリズムに合うまで繰り返します。
自分の声を録音して元の音声と比べます。distribute, server, cacheなどの単語に特に注意しましょう。

シャドーイングとは？英語上達に効果的な理由

シャドーイング（Shadowing）は、もともとプロの通訳者養成プログラムで開発された言語学習法で、多言語習得者として知られるDr. Alexander Arguelles によって広く普及されました。方法はシンプルですが非常に効果的：ネイティブスピーカーの英語を聞きながら、1〜2秒の遅延で声に出してすぐに繰り返す——まるで「影（shadow）」のように話者を追いかけます。文法ドリルや受動的なリスニングと異なり、シャドーイングは脳と口の筋肉が同時にリアルタイムで英語を処理・再現することを強制します。研究により、発音精度、抑揚、リズム、連音、リスニング力、そして会話の流暢さが大幅に向上することが確認されています。IELTSスピーキング対策や自然な英語コミュニケーションを目指す方に特におすすめです。

シャドーイングのやり方: ステップ別の完全ガイドを読む →

シャドーイング練習: Top 5 Redis Use Cases - 動画で英語スピーキングを学ぶ

練習モードを選ぶ

アプリをダウンロード

同じチャンネル

The Secret Sauce Behind NoSQL: LSM Tree

Proxy vs Reverse Proxy (Real-world Examples)

Cache Systems Every Developer Should Know

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

8 Most Important System Design Concepts You Should Know

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

CAP Theorem Simplified

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

System Design: Why is Kafka Popular?

System Design: Why is Kafka fast?

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

What is API Gateway?

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

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

Kubernetes Explained in 6 Minutes | k8s Architecture

How Does a URL Shortener Work?

How Git Works: Explained in 4 Minutes

おすすめ動画

Redis Crash Course - the What, Why and How to use Redis as your primary database

Use these CSS features instead of JavaScript

Rate Limiter System Design in Under 60 Seconds #techprep #programming #systemdesign

Armchair Architects: Resiliency in the Cloud – Core Patterns

How I deploy serverless containers for free

Traceroute: You're Probably Reading the Results Wrong

He Realized his Mistake

Research Source Mastery: How to Find & Verify Credible Data (2026)

Database Sharding! Designing Data-Intensive Applications chapter 6

LangChain in 5 Minutes (Explained Clearly)