Shadowing Practice: System Design: Why is Kafka Popular? - Learn English Speaking with Video
Creando lección...
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.
📺 Mismo canal
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
C12
Cache Systems Every Developer Should Know
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
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
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
✨ Recomendar Video
C11
309 oraciones
Claude Code: The Advanced Guide (99% of Devs Skip These Features)
Business EnglishUniversity StudentsWorking Adults
C14
164 oraciones
System Design Mock Interview: Design Facebook Messenger
Business EnglishUniversity StudentsWorking Adults
C11
186 oraciones
Why Shopify Moved Inventory Reservations from Redis to MySQL
Business EnglishUniversity StudentsWorking Adults
C11
28 oraciones
Kubernetes Explained in 100 Seconds
American AccentBusiness EnglishUniversity StudentsWorking Adults
C12
204 oraciones
Kafka Tutorial for Beginners | Everything you need to get started
Business EnglishUniversity StudentsWorking Adults
C12
339 oraciones
Easy Migration from Postgres to Databricks Lakebase
Business EnglishUniversity StudentsWorking Adults
C12
18 oraciones
SD91: Reliability vs Scalability
Business EnglishUniversity StudentsWorking Adults
C18
102 oraciones
World Models explained in 10min..
Business EnglishUniversity StudentsWorking Adults
C13
176 oraciones
Is Amazon Too Big?
Business EnglishDaily ConversationUniversity Students
C12
11 oraciones
What are Design Patterns? | Introduction to Design Patterns and Principles | Geekific
Business EnglishUniversity StudentsWorking Adults
Vocabulario y notas de pronunciación para esta lección
Esta lección de conversación de nivel C1 se basa en el vídeo “System Design: Why is Kafka Popular?”. Las palabras que más se repiten: Kafka, partition, message, consumer, event. Este vídeo tiene 86 frases y 1080 palabras para practicar shadowing. La parte hablada dura 7:38. El hablante mantiene un ritmo constante de unas 142 palabras por minuto, cómodo para el shadowing. Solo el 75 % de las palabras está entre las 3.000 más comunes del inglés, por lo que el vocabulario es exigente.
Vocabulario clave de este vídeo
Las 15 palabras más avanzadas del vídeo, con su pronunciación y significado:
| Palabra | Pronunciación | Significado |
|---|---|---|
| partition sustantivo | /pɑɹˈtɪ.ʃən/ | parte |
| broker sustantivo | /ˈbɹoʊkɚ/ | corredor, bróker |
| decouple verbo | [diːˈkʌpəɫ] | desacoplar |
| replica sustantivo | /ˈɹɛplɪkə/ | réplica, trasunto |
| absorb verbo | /æbˈsɔɹb/ | absorber |
| replay sustantivo | /ˈɹiːpleɪ/ | repetición |
| disk sustantivo | /dɪsk/ | disco |
| independently adverbio | /ˌɪndɪˈpɛndəntli/ | independientemente |
| append verbo | /ʌˈpɛnd/ | apostillar, enserir |
| blockbuster sustantivo | /ˈblɑkˌbʌs.tɚ/ | bombazo |
| debug verbo | /diːˈbʌɡ/ | depurar |
| overwhelm verbo | /ˌoʊ.vɚˈwɛlm/ | apabullar, arrollar |
| throughput sustantivo | /ˈθɹuː.pʊt/ | tasa de datos, tasa de transferencia |
| follower sustantivo | /ˈfɒləʊə(ɹ)/ | seguidor |
| warp sustantivo | /ˈwɔːp/ | alabeo, pandeo |
Phrasal verbs que vas a escuchar
| Palabra | Significado |
|---|---|
| fall apart verbo | despedazarse, desintegrarse |
| pay off verbo | valer la pena, salir a cuenta |
| take over verbo | apoderarse, enseñorearse |
| work around verbo | baipasear, circunvalar |
Gramática en este vídeo
Las estructuras que más usa el hablante, con las palabras exactas del vídeo:
| Estructura | En el vídeo |
|---|---|
| Oraciones de relativo who / which + oración — información extra sobre una persona o cosa | partition, which is · topics, which are · offsets, which are |
| Voz pasiva be + participio pasado — importa lo que ocurre, no quién lo hace | is sponsored · are stuck |
Pronunciación a tener en cuenta
El hablante usa 4 contracciones y formas reducidas, como don't, isn't, we'll. Dilas en su forma corta, tal como las oyes.
- Los sonidos de “th”: throughput /ˈθɹuː.pʊt/, bandwidth /ˈbændwɪdθ/
- Los sonidos de “sh” y “zh”: partition /pɑɹˈtɪ.ʃən/, aggregation /æɡɹəˈɡeɪʃən/, replication /ɹɛplɪˈkeɪʃən/, hash /ˈhæʃ/, retention /ɹɪˈtɛnʃən/
- Palabras largas — cuida el acento: 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ə/
Sonidos difíciles para hispanohablantes:
- s + consonante al inicio — sin añadir una “e” delante: spike /spaɪk/, sponsor /ˈspɒn.səː/, stack /stæk/
- /v/ — no es /b/: los dientes tocan el labio inferior: overwhelm /ˌoʊ.vɚˈwɛlm/, evolve /ɪˈvɑlv/, behavioral /bɪˈheɪvjəɹəl/, verify /ˈvɛɹɪfaɪ/
- /z/ — sonora, no /s/: optimize /ˈɑptɪmaɪz/, organize /ˈɔɹɡənaɪz/
Cómo practicar con este vídeo
- Escucha el vídeo entero una vez sin hablar y anota las palabras que no conoces.
- Haz shadowing frase por frase a velocidad normal, repitiendo cada una hasta que tu ritmo coincida con el del hablante.
- Grábate y compara con el original, prestando atención a palabras como partition, broker, decouple.
¿Qué es la Técnica de Shadowing?
Shadowing es una técnica de aprendizaje de idiomas respaldada por la ciencia, desarrollada originalmente para la formación de intérpretes profesionales y popularizada por el políglota Dr. Alexander Arguelles. El método es simple pero poderoso: escuchas audio en inglés nativo y lo repites en voz alta de inmediato, como una sombra que sigue al hablante con solo 1-2 segundos de retraso. A diferencia de la escucha pasiva o los ejercicios de gramática, el shadowing obliga a tu cerebro y músculos de la boca a procesar y reproducir simultáneamente patrones de habla reales. Las investigaciones muestran que mejora significativamente la precisión de la pronunciación, la entonación, el ritmo, el habla conectada, la comprensión auditiva y la fluidez al hablar, convirtiéndola en una de las metodologías más efectivas para la preparación del IELTS Speaking y la comunicación en inglés en el mundo real.