Pratique du Shadowing: Top 5 Redis Use Cases - Apprendre l'anglais à l'oral avec la vidéo
Choisissez un mode d'entraînement
Chaque mode ouvre une salle d'entraînement en plein écran.
75 phrases
Si les phrases sont trop courtes ou trop longues, cliquez sur Edit pour les ajuster.
1
In this video, we discover the versatility of Redis.
2
We'll talk about the top use cases that have been better tested in production at various companies and at various scales.
3
Get insights into how Redis solves interesting scalability challenges for us
4
and learn why it is a great tool to know well in our system design toolset.
5
Let's dive right into it.
6
First of all, what is Redis and why do people use it?
7
Redis is an in -memory data structure store.
8
It is most commonly used as a cache.
9
It supports many data structures such as strings, hashes, lists, sets, and sorted sets.
10
Redis is known for its speed.
11
We made a video to explain why Redis is so fast.
12
Look for the link in the description if you would like to watch that video.
13
Now let's dive into the top use cases of Redis.
14
The number one use case of Redis is caching objects to speed up web applications.
15
In this use case, Redis stores frequently requested data in memory.
16
It allows the web servers to return frequently accessed data quickly.
17
This reduces the load on the database and improves the response time for the application.
18
At scale, the cache is distributed among a cluster of Redis servers.
19
Sharding is a common technique to distribute and caching load evenly across the cluster.
20
Other topics to consider when deploying Redis as a distributed cache include setting a correct TTL
21
and handling thundering hurt on cold start.
22
Another common use case is to use Redis as a session store to share session data among stateless servers.
23
When a user logs into a web application, the session data is stored in Redis,
24
along with a unique session ID that is returned to the client as a cookie.
25
When a user makes a request to the application, the session ID is included in the request,
26
and the stateless web server retrieves the session data from Redis using the ID.
27
It is important to note that Redis is an in -memory database.
28
The session data stored in Redis will be lost if the Redis server restarts.
29
Even though Redis provides persistent options like a snapshot and AOF or append -only file,
30
they allow session data to be saved to disk and reloaded into memory in the event of a restart.
31
These options often take too long to load to be practical.
32
In production, replication is usually used instead.
33
In this case, data is replicated to a backup instance.
34
In the event of a crash of the main instance, the backup instance is quickly promoted to take over the traffic.
35
The next use case is distributed log.
36
Distributed logs are used when multiple nodes in an application need to coordinate access to some shared resource.
37
Redis is used as a distributed log with its atomic commands like set -nx or set -if -not -exists.
38
It allows a caller to set a key only if it does not already exist.
39
Here's how it works at a high level.
40
Client 1 tries to acquire the log by setting a key with a unique value
41
and a timeout using the set -nx command.
42
If the key was not already set, the set -nx command returns 1, indicating that the log has been acquired by client 1.
43
Client 1 finishes its work and releases the log by deleting the key.
44
Now if the key was already set, the set -annex command returns 0, indicating that the log has already been held by another client.
45
In this case, client 1 waits and retries the set -annex operation until the log is released by the other client.
46
Note that this simple implementation might be good enough for many use cases, but it is not completely fault -tolerant.
47
For production use, there are many Redis client libraries that provide high -quality distributed log implementation built right off the box.
48
Next up is Ray Limiter.
49
Redis can be used as a Ray Limiter by using its increment command on some counters
50
and setting expiration times on those counters.
51
A very basic
52
Ray Limiting algorithm works this way.
53
For each incoming request, the request IP or user ID is used as a key.
54
The number of requests for the key is incremented using the increment command in Redis.
55
The current count is compared to the allowed rate limit.
56
If the count is within the rate limit, the request is processed.
57
If the count is over the limit, the request is rejected.
58
The keys are set to expire after a specific time window, for example, a minute, to reset the cans for the next time window.
59
More sophisticated rate limiters, like the leaky bucket algorithm, can also be implemented using Redis.
60
The last use case we would like to talk about is gaming leaderboard.
61
For most games that are not super high scale, Redis is a delightful way to implement various types of gaming leaderboards.
62
Sort of sets are the fundamental data structure that enables this.
63
A sort of set is a collection of unique elements, each with a score associated with it.
64
The elements are sorted by score.
65
This allows for quick retrieval of the elements by score in logarithmic time.
66
That's it for our top Redis use cases.
67
Redis is very versatile.
68
There are many different ways to use it.
69
Some features are more better tested than others.
70
Our creativity is the limit.
71
Use it with care and have fun with it.
72
You would like our videos.
73
You may like our weekly system design newsletter as well.
74
It covers topics and trends in large -scale system design, trusted by 200 ,000 readers.
75
Subscribe at blog .buybygo .com.
Télécharger l'application
Tout pour parler couramment
Prononciation IAChaque phrase notée
Phonétique (IPA)Maîtrisez chaque son
VocabulaireEnrichissez votre lexique
Jeu de vocabulaireApprenez en jouant
📺 Même chaîne
C11
The Secret Sauce Behind NoSQL: LSM Tree
Daily ConversationUniversity StudentsWorking Adults
C13
Proxy vs Reverse Proxy (Real-world Examples)
Daily ConversationUniversity StudentsWorking Adults
C12
Cache Systems Every Developer Should Know
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
C150
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
✨ Vidéo recommandée
C1231 phrases
Redis Crash Course - the What, Why and How to use Redis as your primary database
Daily ConversationUniversity StudentsWorking Adults
C12
185 phrases
Use these CSS features instead of JavaScript
Daily ConversationUniversity StudentsWorking Adults
C13
9 phrases
Rate Limiter System Design in Under 60 Seconds #techprep #programming #systemdesign
Daily ConversationUniversity StudentsWorking Adults
C11
180 phrases
Armchair Architects: Resiliency in the Cloud – Core Patterns
Daily ConversationUniversity StudentsWorking Adults
C11
78 phrases
How I deploy serverless containers for free
Daily ConversationUniversity StudentsWorking Adults
C11
54 phrases
Traceroute: You're Probably Reading the Results Wrong
Daily ConversationUniversity StudentsWorking Adults
C11
202 phrases
He Realized his Mistake
Daily ConversationUniversity Students
B210
30 phrases
Research Source Mastery: How to Find & Verify Credible Data (2026)
Daily ConversationUniversity Students
C11
689 phrases
Database Sharding! Designing Data-Intensive Applications chapter 6
Daily ConversationUniversity StudentsWorking Adults
C11
74 phrases
LangChain in 5 Minutes (Explained Clearly)
Daily ConversationUniversity StudentsWorking Adults
Vocabulaire et conseils d’expression pour cette leçon
Cette leçon d’expression orale s’appuie sur la vidéo « Top 5 Redis Use Cases ». Les mots qui reviennent le plus souvent : Redis, log, client, session, key. Cette vidéo contient 75 phrases et 937 mots à répéter en shadowing. La partie parlée dure 6:16. Le locuteur parle à un rythme régulier d’environ 149 mots par minute, confortable pour le shadowing. Seuls 77 % des mots font partie des 3 000 mots les plus courants en anglais, le vocabulaire est donc exigeant.
Vocabulaire clé de cette vidéo
15 mots de la vidéo à retenir, avec leur prononciation et leur sens :
| Mot | Prononciation | Sens |
|---|---|---|
| distribute verbe | /dɪˈstɹɪbjuːt/ | distribuer |
| server nom | /ˈsɝvɚ/ | serveur |
| cache nom | /kæʃ/ | cache, mémoire cache |
| element nom | /ˈɛləmənt/ | élément |
| topic nom | /ˈtɑpɪk/ | sujet, thème |
| log nom | /lɔɡ/ | grume, tronc |
| indicate verbe | /ˈɪndɪˌkeɪt/ | indiquer, signaler |
| database nom | /ˈdeɪtəˌbeɪs/ | base de données, banque de données |
| implementation nom | /ˌɪmplɪmənˈteɪʃən/ | mise en œuvre |
| backup nom | /ˈbækˌʌp/ | remplaçant |
| implement verbe | /ˈɪmpləmənt/ | appliquer, exécuter |
| acquire verbe | /əˈkwaɪɚ/ | acquérir |
| dive verbe | /daɪv/ | nager, plonger |
| algorithm nom | /ˈælɡəɹɪðm̩/ | algorithme |
| cluster nom | /ˈklʌstɚ/ | groupe |
Les verbes à particule que vous entendrez
| Mot | Prononciation | Sens |
|---|---|---|
| speed up verbe | /spiːdˈʌp/ | accélérer |
| take over verbe | reprendre |
La grammaire de cette vidéo
Les structures que le locuteur utilise le plus, avec les mots exacts de la vidéo :
| Structure | Dans la vidéo |
|---|---|
| Voix passive be + participe passé — l’accent est mis sur ce qui arrive, pas sur qui le fait | is known · is distributed · is stored |
| Present perfect have/has + participe passé — une action passée qui compte encore maintenant | have been · has been acquired · has already been held |
Prononciation à surveiller
- Les sons « th »: algorithm /ˈælɡəɹɪðm̩/, thunder /ˈθʌndɚ/, logarithmic /ˌlɒɡəˈɹɪðmɪk/
- Les sons « sh » et « zh »: cache /kæʃ/, implementation /ˌɪmplɪmənˈteɪʃən/, associate /əˈsoʊʃi.ət/, hash /ˈhæʃ/, expiration /ˌɛk.spɚˈeɪ̯.ʃən/
- Mots longs — placez bien l’accent: 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/
Les sons difficiles pour les francophones :
- /r/ anglais — langue recourbée, sans frotter la gorge: distribute /dɪˈstɹɪbjuːt/, algorithm /ˈælɡəɹɪðm̩/, restart /ˈɹiːˌstɑɹt/, practical /ˈpɹæk.tɪ.kəl/, string /stɹɪŋ/
- /ŋ/ final — sans prononcer de /g/ après: string /stɹɪŋ/, incoming /ˈɪnˌkʌmɪŋ/
Comment s’entraîner avec cette vidéo
- Écoutez la vidéo en entier une fois sans parler et notez les mots que vous ne connaissez pas.
- Répétez phrase par phrase à vitesse normale, en reprenant chacune jusqu’à ce que votre rythme corresponde à celui du locuteur.
- Enregistrez-vous et comparez avec l’original, en faisant attention à des mots comme distribute, server, cache.
Qu'est-ce que la technique du Shadowing ?
Le Shadowing est une technique d'apprentissage des langues fondée sur la science, développée à l'origine pour la formation des interprètes professionnels. Le principe est simple mais puissant : vous écoutez de l'anglais natif et le répétez immédiatement à voix haute — comme une ombre suivant le locuteur avec un décalage de 1 à 2 secondes. Les recherches montrent une amélioration significative de la précision de la prononciation, de l'intonation, du rythme, des liaisons, de la compréhension orale et de la fluidité.