Shadowing Practice: System Design: Why is Kafka fast? - Learn English Speaking with Video
Ders oluşturuluyor...
1
Why is Kafka fast?
2
What is the secret?
3
We will talk about it in this video.
4
Let's dive right in.
5
We'll first start by acknowledging that the term fast is ambiguous.
6
What does it even mean that Kafka is fast?
7
Are we talking latency?
8
Are we talking throughput?
9
Is fast compared to what?
10
Kafka is optimized for high throughput.
11
It is designed to move a large number of records in a short amount of time.
12
Think of it as a very large pipe moving liquid.
13
The bigger the diameter of the pipe, the larger the volume of liquid that can move through it.
14
So when someone says Kafka is fast, they usually refer to Kafka's ability to move a lot of data efficiently.
15
What are some of the design decisions that help Kafka move a lot of data quickly?
16
There are many design decisions that contributed to Kafka's performance.
17
In this video, we'll focus on two.
18
We think these two carry the most weight.
19
The first one is Kafka's reliance on sequential I.O.
20
What is sequential I.O.?
21
Let's dig deeper into that.
22
There's a common misconception that disk access is slow compared to memory access.
23
But this largely depends on data access patterns.
24
There are two types of disk access patterns, random and sequential.
25
For hard drives, it takes time to physically move the arm to different locations on the magnetic disks.
26
This is what makes random access slow.
27
For sequential access though, since the arm doesn't need to jump around it is much faster to read
28
and write blocks of data one after the other kafka takes
29
advantage of this by using an append only log as its primary data structure
30
and the pen only log adds new data to the end
31
of the file this access pattern is sequential now let's bring
32
this idea home with some numbers on modern hardware with an
33
array of this hard disks sequential will write reach hundreds of megabytes per second,
34
while random writes are measured in hundreds of kilobytes per second.
35
Sequential access is several order of magnitude faster.
36
Using hard disks has its cost advantage too.
37
Compared to SSD, hard disks come as one-third of the price, but with about three times the capacity.
38
Giving Kafka a large pool of cheap disk space without any performance penalty, means that Kafka can cost-effectively retain messages for a long period of time,
39
a feature that was uncommon to messaging systems before Kafka.
40
The second design choice that gives Kafka its performance advantage is its focus on efficiency.
41
Kafka has moved a lot of data from network to disk and then from disk to network.
42
It is critically important to eliminate excess copy when moving pages and pages of data between the disk and the network.
43
This is where zero copy principle comes into the picture.
44
Modern Unix operating systems are highly optimized to transfer data from disk to network without copying data excessively.
45
Let's dive deeper to see how this is done.
46
First, we look at how Kafka sends a page of data on disk to the consumer
47
when zero copy is not used at all.
48
First, the data is loaded from disk to the OS cache.
49
Second, the data is copied from the OS cache into the Kafka application.
50
Third, the data is copied from Kafka to the socket buffer.
51
And fourth, the data is copied from the socket buffer to the network interface card buffer.
52
And finally, the data is sent over the network to the consumer.
53
Now this is clearly inefficient.
54
There are four copies and two system calls.
55
Now let's compare this to zero copy.
56
The first step is the same.
57
The data page is loaded from the disk to the OS cache.
58
With zero copy, the Kafka application uses a system call called send file to
59
tell the operating system to directly copy the data from the OS cache to the network interface card buffer.
60
In this optimized path, the only copy is from the OS cache into the network card buffer.
61
With a modern network card, this copying is done with DMA.
62
DMA stands for Direct Memory Access.
63
When DMA is used, the CPU is not involved, making it even more efficient.
64
To recap, sequential I.O and zero copy principle are the cornerstone to Kafka's high performance.
65
Kafka uses other techniques to squeeze every ounce of performance of modern hardware, but these two are the most important in our view.
66
If you'd like to learn more about system design, check out our books and weekly newsletter.
67
Please subscribe if you learned something new.
68
Thank you so much and we'll see you next time.
📺 Aynı Kanal
C11
The Secret Sauce Behind NoSQL: LSM Tree
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
System Design: Why is Kafka Popular?
Business EnglishUniversity StudentsWorking Adults
C12
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
C12
What Are Microservices Really All About? (And When Not To Use It)
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
✨ Video Öner
C166
50 cümleler
Psychology of Intelligence: Learn Faster Than Everyone Around You
Business EnglishUniversity StudentsWorking Adults
C132 cümleler
Linus Torvalds Explains What Makes Linux So Fast
Business EnglishUniversity StudentsWorking Adults
C11
346 cümleler
Trust the Process: How to Design Teams That Actually Work
Business EnglishUniversity StudentsWorking Adults
C11
689 cümleler
Database Sharding! Designing Data-Intensive Applications chapter 6
Business EnglishUniversity StudentsWorking Adults
C11
114 cümleler
Design a File Upload Service Like a Senior Engineer
Business EnglishUniversity StudentsWorking Adults
C13
26 cümleler
🔥 Java Multithreading Rapid Fire | Can You Answer These Interview Questions? #shorts
Business EnglishInterview EnglishUniversity Students
C115
29 cümleler
Amazon Athena explained in 120 seconds💡
Business EnglishUniversity StudentsWorking Adults
C12
162 cümleler
Crypto Agility Explained: Protect Data from Quantum Computing Threats
Business EnglishUniversity StudentsWorking Adults
C12
131 cümleler
Unit Conversion & Significant Figures: Crash Course Chemistry #2
Business EnglishUniversity StudentsWorking Adults
C11
133 cümleler
Data Ingestion Best Practices! How to Ingest Data Efficiently at Enterprise Scale!
Business EnglishUniversity StudentsWorking Adults
Bu dersin kelimeleri ve konuşma notları
Bu videoda gölgeleme çalışması için 68 cümle ve 782 kelime var. Konuşma bölümü 4:56 sürüyor. Konuşmacı dakikada yaklaşık 159 kelimeyle, günlük konuşmaya yakın doğal bir hızda konuşuyor. Kelimelerin yalnızca %80’i İngilizcede en sık kullanılan 3.000 kelime arasında, bu yüzden kelime dağarcığı zorlayıcı.
Bu videodaki önemli kelimeler
Videodan öğrenmeye değer 15 kelime, telaffuzu ve anlamıyla:
| Kelime | Telaffuz | Anlam |
|---|---|---|
| disk isim | /dɪsk/ | disk, ağırşak |
| cache isim | /kæʃ/ | önbellek |
| compare fiil | /kəmˈpɛɚ/ | karşılaştırmak, kıyaslamak |
| liquid isim | /ˈlɪk.wɪd/ | sıvı, likit |
| principle isim | /ˈpɹɪn.sɪ.pəl/ | prensip, ilke |
| hardware isim | /ˈhɑɹdˌwɛɹ/ | hırdavat |
| pipe isim | /ˈpaɪp/ | düdük, kaval |
| dive fiil | /daɪv/ | dalmak |
| interface isim | /ˈɪn(t)ɚˌfeɪs/ | arayüz |
| socket isim | /ˈsɑkɪt/ | priz |
| technique isim | /tɛkˈniːk/ | teknik |
| refer fiil | /ɹɪˈfɜː/ | zikretmek |
| efficient sıfat | /ɪˈfɪʃənt/ | verimli |
| efficiency isim | /ɪˈfɪʃ.ən.si/ | verimlilik |
| excess isim | /ˈɛksɛs/ | fazlalık, şiddet |
Duyacağınız deyimsel fiiller
| Kelime | Anlam |
|---|---|
| check out fiil | gözden geçirmek |
Dikkat edilecek telaffuzlar
Konuşmacı we'll, doesn't, you'd gibi kısaltılmış biçimleri 5 kez kullanıyor. Bunları duyduğunuz gibi kısa söyleyin.
- “sh” ve “zh” sesleri: cache /kæʃ/, efficient /ɪˈfɪʃənt/, efficiency /ɪˈfɪʃ.ən.si/, inefficient /ˌɪn.ɪˈfɪʃ.ənt/, misconception /ˌmɪs.kənˈsɛp.ʃən/
- Uzun kelimeler — vurguyu doğru yere koyun: efficiency /ɪˈfɪʃ.ən.si/, eliminate /ɪˈlɪm.ɪ.neɪt/, diameter /daɪˈæmɪdɚ/, critically /ˈkɹɪt.ɪ.kə.li/, ambiguous /æmˈbɪɡ.ju.əs/
Bu videoyla nasıl çalışılır
- Videonun tamamını konuşmadan bir kez dinleyin ve bilmediğiniz kelimeleri not edin.
- 0,75× hızla başlayın, cümle cümle tekrar edin ve kolaylaşınca normal hıza dönün.
- Kendinizi kaydedin ve orijinaliyle karşılaştırın; disk, cache, compare gibi kelimelere özellikle dikkat edin.
Gölgeleme Tekniği Nedir?
Gölgeleme, başlangıçta profesyonel tercüman eğitimi için geliştirilen ve çok dilli Dr. Alexander Arguelles tarafından popüler hale getirilen, bilim destekli bir dil öğrenme tekniğidir. Yöntem basit ama güçlüdür: ana dili İngilizce olan bir sesi dinler ve hemen yüksek sesle tekrar edersiniz — konuşmacıyı 1-2 saniye gecikmeyle takip eden bir gölge gibi. Pasif dinleme veya dilbilgisi alıştırmalarının aksine, gölgeleme beyninizi ve ağız kaslarınızı gerçek konuşma kalıplarını eşzamanlı olarak işlemeye ve yeniden üretmeye zorlar. Araştırmalar, telaffuz doğruluğu, tonlama, ritim, bağlı konuşma, dinleme anlama ve konuşma akıcılığını önemli ölçüde geliştirdiğini göstermektedir — bu da onu IELTS Konuşma hazırlığı ve gerçek dünya İngilizce iletişimi için en etkili yöntemlerden biri yapar.