Shadowing Practice: System Design: Why is Kafka Popular? - Learn English Speaking with Video
Les maken...
1
Why do LinkedIn, Netflix, and Uber all use Kafka to handle boolean messages per day?
2
It's not just about scale.
3
Kafka's distributed log design offers something unique, the ability to replay events, decouple services, and absorb traffic spikes.
4
In this video, we'll look at how Kafka achieves this and what trade-offs you are making when you use it.
5
The main reason companies use Kafka is to decouple their systems.
6
Instead of having services talk directly to each other, they communicate through Kafka.
7
This means producers and consumers can evolve independently, and Kafka absorbs traffic spikes that would otherwise overwhelm your systems.
8
It also enables replay for debugging and recovery when things go wrong.
9
So how does this distributed log actually work?
10
When you send a message to Kafka, it gets written to a partition, which is basically append-only log files sitting on disk.
11
These partitions live on servers called brokers, and when you put multiple brokers together, you get a Kafka cluster.
12
Partitions organize into topics, which are categories for your messages.
13
You might have a topic for payments, another for user clicks, and another for video uploads.
14
Producers write messages into topics, and consumers read them.
15
Every message contains a key, a value, a timestamp, and sometimes headers for metadata.
16
The key determines which partition your message lands in.
17
If you send multiple messages with the same key, they will always go to the same partition and stay in order.
18
When you don't provide a key, Kafka spreads messages around to balance the load across partitions.
19
A single broker on modern hardware can handle hundreds of thousands of messages per second
20
and store as much data as your disk can hold.
21
In practice though, the broker will usually hit network bandwidth limits before CPU or the disk becomes the bottleneck.
22
Today's video is sponsored by Warped, the best way to code with AI agents.
23
Too often, agents write code that's almost right, leaving developers stuck debugging instead of shipping.
24
Warped is different.
25
Ranked top of Terminal Bench and SWE Bench verified.
26
Warped's agent understands your context and writes production-ready code out of the box.
27
Prom, reveal, and refine all in one interface.
28
No context switching, no wasted time.
29
You stay in control.
30
And it pays off.
31
On average, users are saving over an hour a day with warp.
32
Download warp by clicking the link in the description.
33
Partitioning strategy is what determines whether your system scales gracefully or falls apart under low.
34
Pick the wrong partition key and you will end up with hard partitions, where one partition gets hammered while the others sit idle.
35
Imagine you're building a streaming service and you partition by movie ID.
36
Everything works fine until Friday night when a blockbuster drops and suddenly millions of users are streaming the same movie.
37
All these events hit the same partition and your system starts choking.
38
The solution is to use compound keys.
39
Combine the movie ID with a hash of the user ID
40
and now events for that blockbuster get spread across multiple partitions while each user sessions stay in order.
41
There are other partitioning schemes too, each with its own trade-offs.
42
For example, time-based partitions work great for log data because they make retention policies simple, but they complicate real-time aggregation.
43
Consumers track their progress through partitions using offsets, which are basically bookmarks to tell you which message you last processed.
44
They save these offsets back to Kafka periodically, so if they crash, they know exactly where to pick The timing of these commits matters.
45
Commit too early and you might lose messages if you crash.
46
Commit too late and you might process the same message twice.
47
Consumer groups let multiple consumers work together, with Kafka making sure each message gets processed by exactly one consumer in the group.
48
If a consumer fails, Kafka reassigns its partition to the surviving consumers through rebalancing.
49
It handles most failure scenarios without any manual intervention.
50
Kafka offers three delivery guarantees.
51
At most one is fast, but might lose messages.
52
At least once ensures no loss but might produce duplicates.
53
Exactly once is possible, but it is complicated to set up and run slower.
54
Durability comes with replication.
55
Every partition has one leader that handles all reads and writes, plus several followers that copy everything the leader does.
56
If the leader fails, one of the followers takes over.
57
Most production systems run with three replicas, which means you can lose a broker and still have backup.
58
You can configure Kafka to wait for all active replicas to acknowledge rights before considering them successful.
59
This gives you maximum safety but slows things down.
60
With three replicas, you can typically survive one broker failure without losing data.
61
These mechanics enable powerful patterns in production.
62
At Uber, location updates for millions of drivers reportedly flow through Kafka to calculate search pricing in real time.
63
They partition geographically so each region can scale independently.
64
Some companies use Kafka as their source of truth for data.
65
Instead of updating database records directly, they append every state change as an event to Kafka.
66
Want the current state?
67
We play the events.
68
This pattern, called event sourcing, gives you a complete audit trail of everything that happened in your system.
69
But Kafka isn't the right choice for every use case.
70
It optimizes for throughput, not latency.
71
The batching and buffering that enables high throughput adds some delay, making it unsuitable for request response patterns.
72
Kafka only guarantees order within a single partition, not across an entire topic.
73
If you absolutely need global ordering, you are stuck with a single partition, which kills your ability to parallelize.
74
Most systems work around this by accepting partial ordering.
75
Exactly once processing requires careful setup on both producer and consumer size,
76
but when you need it for financial transactions or critical data pipelines, the complexity is worth it.
77
Kafka works because it decouples producers from consumers, letting them evolve independently without breaking each other.
78
Traffic spies that would overwhelm a direct connection get absorbed by the log.
79
When something goes wrong in production, you can replay events to see exactly what happened.
80
But this power comes with a cost.
81
Kafka adds significant operational complexity to your stack.
82
Ready to age your next technical interview?
83
Join our community where we offer comprehensive courses on system design, coding, behavioral questions, machine learning, and object-oriented design.
84
Learn more at bytebytego.com.
85
Thank you.
86
Thank you.
📺 Zelfde Kanaal
C11
The Secret Sauce Behind NoSQL: LSM Tree
Business EnglishUniversity StudentsWorking Adults
C13
Proxy vs Reverse Proxy (Real-world Examples)
Business EnglishUniversity StudentsWorking Adults
C13
System Design Was HARD - Until You Knew the Trade-Offs
Business EnglishUniversity StudentsWorking Adults
C17
8 Most Important System Design Concepts You Should Know
Business EnglishUniversity StudentsWorking Adults
C13
Everything You Need to Know About DNS: Crash Course System Design #4
Business EnglishUniversity StudentsWorking Adults
C12
CAP Theorem Simplified
Business EnglishUniversity StudentsWorking Adults
C12
What Is REST API? Examples And How To Use It: Crash Course System Design #3
Business EnglishUniversity StudentsWorking Adults
C12
What is API Gateway?
Business EnglishUniversity StudentsWorking Adults
C15
What Are Microservices Really All About? (And When Not To Use It)
Business EnglishUniversity StudentsWorking Adults
C11
System Design: Why is Kafka fast?
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
✨ Aanbevolen Video
C11
392 zinnen
Uber Data Engineering Mock Interview - Ride-Sharing Data Warehouse Schema
Business EnglishInterview EnglishUniversity Students
C11
78 zinnen
How I deploy serverless containers for free
Business EnglishUniversity StudentsWorking Adults
C11
85 zinnen
AI Can Write Code. And That’s the Problem.
Business EnglishUniversity StudentsWorking Adults
C11
176 zinnen
Every Networking Concept Explained | Networking 101 (2026)
Business EnglishUniversity StudentsWorking Adults
C1231 zinnen
Redis Crash Course - the What, Why and How to use Redis as your primary database
Business EnglishUniversity StudentsWorking Adults
C11
96 zinnen
Design Patterns in Java Theory
Business EnglishUniversity StudentsWorking Adults
C14
164 zinnen
System Design Mock Interview: Design Facebook Messenger
Business EnglishUniversity StudentsWorking Adults
C11
133 zinnen
Data Ingestion Best Practices! How to Ingest Data Efficiently at Enterprise Scale!
Business EnglishUniversity StudentsWorking Adults
C12
4 zinnen
What is Event Driven Architecture (EDA)?
Business EnglishUniversity StudentsWorking Adults
C115
29 zinnen
Amazon Athena explained in 120 seconds💡
Business EnglishUniversity StudentsWorking Adults
Woordenschat en spreektips bij deze les
Deze spreekles op niveau C1 is gebaseerd op de video “System Design: Why is Kafka Popular?”. Deze woorden komen het vaakst terug: Kafka, partition, message, consumer, event. Deze video bevat 86 zinnen en 1080 woorden om na te spreken. Het gesproken deel duurt 7:38. De spreker praat in een gelijkmatig tempo van ongeveer 142 woorden per minuut, prettig om te shadowen. Slechts 75% van de woorden hoort bij de 3.000 meest gebruikte Engelse woorden, dus de woordenschat is pittig.
Belangrijke woorden in deze video
De 15 moeilijkste woorden uit de video, met uitspraak en betekenis:
| Woord | Uitspraak | Betekenis |
|---|---|---|
| partition zelfstandig naamwoord | /pɑɹˈtɪ.ʃən/ | opdeling, partitie |
| broker zelfstandig naamwoord | /ˈbɹoʊkɚ/ | tussenpersoon, makelaar |
| decouple werkwoord | [diːˈkʌpəɫ] | ontkoppelen |
| absorb werkwoord | /æbˈsɔɹb/ | absorberen, (in zich) opnemen |
| disk zelfstandig naamwoord | /dɪsk/ | schijf |
| independently bijwoord | /ˌɪndɪˈpɛndəntli/ | onafhankelijk |
| append werkwoord | /ʌˈpɛnd/ | hechten, aanhechten |
| blockbuster zelfstandig naamwoord | /ˈblɑkˌbʌs.tɚ/ | kaskraker |
| debug werkwoord | /diːˈbʌɡ/ | debuggen |
| overwhelm werkwoord | /ˌoʊ.vɚˈwɛlm/ | overweldigen, overmannen |
| follower zelfstandig naamwoord | /ˈfɒləʊə(ɹ)/ | volger, navolger |
| warp zelfstandig naamwoord | /ˈwɔːp/ | vervorming |
| distribute werkwoord | /dɪˈstɹɪbjuːt/ | verdelen |
| evolve werkwoord | /ɪˈvɑlv/ | ontwikkelen |
| spike zelfstandig naamwoord | /spaɪk/ | stekel |
Phrasal verbs die je zult horen
| Woord | Uitspraak | Betekenis |
|---|---|---|
| fall apart werkwoord | uiteenvallen, uit elkaar vallen | |
| pay off werkwoord | aflossen | |
| set up werkwoord | /ˌsɛt ˈʌp/ | bereiden, voorbereiden |
| 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 |
|---|---|
| Betrekkelijke bijzinnen who / which + zin — extra informatie over een persoon of ding | partition, which is · topics, which are · offsets, which are |
| Lijdende vorm be + voltooid deelwoord — het gaat om wat er gebeurt, niet om wie het doet | is sponsored · is complicated · are stuck |
Uitspraak om op te letten
De spreker gebruikt 4 samentrekkingen en verkorte vormen, zoals don't, isn't, we'll. Spreek ze kort uit, zoals je ze hoort.
- De “th”-klanken: throughput /ˈθɹuː.pʊt/, bandwidth /ˈbændwɪdθ/
- De klanken “sh” en “zh”: partition /pɑɹˈtɪ.ʃən/, aggregation /æɡɹəˈɡeɪʃən/, replication /ɹɛplɪˈkeɪʃən/, hash /ˈhæʃ/, retention /ɹɪˈtɛnʃən/
- Lange woorden — let op de klemtoon: independently /ˌɪndɪˈpɛndəntli/, complexity /kəmˈplɛk.sɪ.ti/, aggregation /æɡɹəˈɡeɪʃən/, durability /dəɹəˈbɪləti/, metadata /ˈmɛt.əˌdeɪ.tə/
Klanken die Nederlandstaligen lastig vinden:
- Stemhebbende eindmedeklinker — /b/, /d/, /g/, /z/, /v/ niet verscherpen: absorb /æbˈsɔɹb/, append /ʌˈpɛnd/, debug /diːˈbʌɡ/, evolve /ɪˈvɑlv/, optimize /ˈɑptɪmaɪz/
- /æ/ — opener dan de Nederlandse “e”: absorb /æbˈsɔɹb/, aggregation /æɡɹəˈɡeɪʃən/, timestamp /ˈtaɪmˌstæmp/, bandwidth /ˈbændwɪdθ/, hash /ˈhæʃ/
- /g/ — een harde plofklank, geen Nederlandse “g”: debug /diːˈbʌɡ/, aggregation /æɡɹəˈɡeɪʃən/, configure /kənˈfɪɡə(ɹ)/, gracefully /ˈɡɹeɪsfəli/, organize /ˈɔɹɡənaɪz/
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 partition, broker, decouple.
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.