Shadowing Practice: Top 5 Redis Use Cases - Learn English Speaking with Video
Kies een oefenmodus
Elke modus opent een volledig scherm oefenruimte.
75 zinnen
Als zinnen te kort of te lang zijn, klik op Bewerken om ze aan te passen.
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.
App downloaden
Alles wat je nodig hebt om vloeiend te spreken
AI UitspraakScoor elke zin
IPA OefeningBeheers elk geluid
WoordenschatBouw je woordenschat op
WoordenspelLeren terwijl je speelt
Zelfde Kanaal
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
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
C150
Kubernetes Explained in 6 Minutes | k8s Architecture
Business EnglishUniversity StudentsWorking Adults
C13
System Design: Why is Kafka Popular?
Business EnglishUniversity StudentsWorking Adults
C14
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
C13
How Does a URL Shortener Work?
Business EnglishInterview EnglishUniversity Students
B2How Git Works: Explained in 4 Minutes
Business EnglishUniversity StudentsWorking Adults
FOR YOU
Aanbevolen Video
C1231 zinnen
Redis Crash Course - the What, Why and How to use Redis as your primary database
Daily ConversationUniversity StudentsWorking Adults
C12
185 zinnen
Use these CSS features instead of JavaScript
Daily ConversationUniversity StudentsWorking Adults
C13
9 zinnen
Rate Limiter System Design in Under 60 Seconds #techprep #programming #systemdesign
Daily ConversationUniversity StudentsWorking Adults
C11
180 zinnen
Armchair Architects: Resiliency in the Cloud – Core Patterns
Daily ConversationUniversity StudentsWorking Adults
C11
847 zinnen
The Complete Guide to Hybrid Search in RAG (BM25 + Embeddings + Reranker)
Daily ConversationUniversity Students
C11
78 zinnen
How I deploy serverless containers for free
Daily ConversationUniversity StudentsWorking Adults
C11
54 zinnen
Traceroute: You're Probably Reading the Results Wrong
Daily ConversationUniversity StudentsWorking Adults
C11
689 zinnen
Database Sharding! Designing Data-Intensive Applications chapter 6
Daily ConversationUniversity StudentsWorking Adults
C11
74 zinnen
LangChain in 5 Minutes (Explained Clearly)
Daily ConversationUniversity StudentsWorking Adults
C11
781 zinnen
How Do I Reverse Brain Rot?
Daily ConversationUniversity StudentsWorking Adults
Woordenschat en spreektips bij deze les
Deze spreekles is gebaseerd op de video “Top 5 Redis Use Cases”. Deze woorden komen het vaakst terug: Redis, log, client, session, key. Deze video bevat 75 zinnen en 937 woorden om na te spreken. Het gesproken deel duurt 6:16. De spreker praat in een gelijkmatig tempo van ongeveer 149 woorden per minuut, prettig om te shadowen. Slechts 77% van de woorden hoort bij de 3.000 meest gebruikte Engelse woorden, dus de woordenschat is pittig.
Belangrijke woorden in deze video
15 woorden uit de video die het leren waard zijn, met uitspraak en betekenis:
| Woord | Uitspraak | Betekenis |
|---|---|---|
| distribute werkwoord | /dɪˈstɹɪbjuːt/ | verdelen |
| server zelfstandig naamwoord | /ˈsɝvɚ/ | server |
| cache zelfstandig naamwoord | /kæʃ/ | cache |
| element zelfstandig naamwoord | /ˈɛləmənt/ | element |
| topic zelfstandig naamwoord | /ˈtɑpɪk/ | onderwerp, thema |
| log zelfstandig naamwoord | /lɔɡ/ | boomstam, boomstronk |
| indicate werkwoord | /ˈɪndɪˌkeɪt/ | aanwijzen, aanduiden |
| database zelfstandig naamwoord | /ˈdeɪtəˌbeɪs/ | database, databank |
| implementation zelfstandig naamwoord | /ˌɪmplɪmənˈteɪʃən/ | implementatie |
| backup zelfstandig naamwoord | /ˈbækˌʌp/ | reserve |
| implement werkwoord | /ˈɪmpləmənt/ | implementeren, (in de praktijk) toepassen |
| acquire werkwoord | /əˈkwaɪɚ/ | verwerven, verkrijgen |
| dive werkwoord | /daɪv/ | duiken, onderwaterzwemmen |
| algorithm zelfstandig naamwoord | /ˈælɡəɹɪðm̩/ | algoritme |
| cluster zelfstandig naamwoord | /ˈklʌstɚ/ | tros |
Phrasal verbs die je zult horen
| Woord | Betekenis |
|---|---|
| take over werkwoord | overnemen |
Grammatica in deze video
De structuren die de spreker het meest gebruikt, met de exacte woorden uit de video:
| Structuur | In de video |
|---|---|
| Lijdende vorm be + voltooid deelwoord — het gaat om wat er gebeurt, niet om wie het doet | is known · is distributed · is stored |
| Present perfect have/has + voltooid deelwoord — iets uit het verleden dat nu nog telt | have been · has been acquired · has already been held |
Uitspraak om op te letten
- De “th”-klanken: algorithm /ˈælɡəɹɪðm̩/, thunder /ˈθʌndɚ/, logarithmic /ˌlɒɡəˈɹɪðmɪk/
- De klanken “sh” en “zh”: cache /kæʃ/, implementation /ˌɪmplɪmənˈteɪʃən/, associate /əˈsoʊʃi.ət/, hash /ˈhæʃ/, expiration /ˌɛk.spɚˈeɪ̯.ʃən/
- Lange woorden — let op de klemtoon: 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/
Klanken die Nederlandstaligen lastig vinden:
- Stemhebbende eindmedeklinker — /b/, /d/, /g/, /z/, /v/ niet verscherpen: log /lɔɡ/, dive /daɪv/, solve /sɒlv/, subscribe /səbˈskɹaɪb/, node /noʊd/
- /æ/ — opener dan de Nederlandse “e”: cache /kæʃ/, backup /ˈbækˌʌp/, algorithm /ˈælɡəɹɪðm̩/, practical /ˈpɹæk.tɪ.kəl/, hash /ˈhæʃ/
- /g/ — een harde plofklank, geen Nederlandse “g”: log /lɔɡ/, algorithm /ˈælɡəɹɪðm̩/, logarithmic /ˌlɒɡəˈɹɪðmɪk/
Zo oefen je met deze video
- Luister de hele video één keer zonder te spreken en noteer de woorden die je niet kent.
- Spreek zin voor zin na op normale snelheid en herhaal elke zin tot je ritme gelijk is aan dat van de spreker.
- Neem jezelf op en vergelijk met het origineel; let daarbij op woorden als distribute, server, cache.
Wat is de Shadowing-techniek?
Shadowing is een wetenschappelijk onderbouwde taalleermethode die oorspronkelijk is ontwikkeld voor professionele tolkentraining en gepopulariseerd door polyglot Dr. Alexander Arguelles. De methode is eenvoudig maar krachtig: je luistert naar native Engelse audio en herhaalt het onmiddellijk hardop — als een schaduw die de spreker volgt met slechts 1–2 seconden vertraging. In tegenstelling tot passief luisteren of grammaticadrills, dwingt shadowing je hersenen en mondspieren om echte spraakpatronen tegelijkertijd te verwerken en te reproduceren. Onderzoek toont aan dat het de uitspraaknauwkeurigheid, intonatie, ritme, verbonden spraak, luisterbegrip en spreekvaardigheid aanzienlijk verbetert — waardoor het een van de meest effectieve methoden is voor IELTS Speaking-voorbereiding en echte Engelse communicatie.