Prática de Shadowing: System Design: Why is Kafka fast? - Aprenda a falar inglês com vídeo

Escolha um modo de prática

Cada modo abre uma sala de prática em tela cheia.

68 frases

Se as frases estiverem muito curtas ou longas, clique em Edit para ajustá-las.

Why is Kafka fast?

What is the secret?

We will talk about it in this video.

Let's dive right in.

We'll first start by acknowledging that the term fast is ambiguous.

What does it even mean that Kafka is fast?

Are we talking latency?

Are we talking throughput?

Is fast compared to what?

Kafka is optimized for high throughput.

It is designed to move a large number of records in a short amount of time.

Think of it as a very large pipe moving liquid.

The bigger the diameter of the pipe, the larger the volume of liquid that can move through it.

So when someone says Kafka is fast, they usually refer to Kafka's ability to move a lot of data efficiently.

What are some of the design decisions that help Kafka move a lot of data quickly?

There are many design decisions that contributed to Kafka's performance.

In this video, we'll focus on two.

We think these two carry the most weight.

The first one is Kafka's reliance on sequential I.O.

What is sequential I.O.?

Let's dig deeper into that.

There's a common misconception that disk access is slow compared to memory access.

But this largely depends on data access patterns.

There are two types of disk access patterns, random and sequential.

For hard drives, it takes time to physically move the arm to different locations on the magnetic disks.

This is what makes random access slow.

For sequential access though, since the arm doesn't need to jump around it is much faster to read

and write blocks of data one after the other kafka takes

advantage of this by using an append only log as its primary data structure

and the pen only log adds new data to the end

of the file this access pattern is sequential now let's bring

this idea home with some numbers on modern hardware with an

array of this hard disks sequential will write reach hundreds of megabytes per second,

while random writes are measured in hundreds of kilobytes per second.

Sequential access is several order of magnitude faster.

Using hard disks has its cost advantage too.

Compared to SSD, hard disks come as one-third of the price, but with about three times the capacity.

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,

a feature that was uncommon to messaging systems before Kafka.

The second design choice that gives Kafka its performance advantage is its focus on efficiency.

Kafka has moved a lot of data from network to disk and then from disk to network.

It is critically important to eliminate excess copy when moving pages and pages of data between the disk and the network.

This is where zero copy principle comes into the picture.

Modern Unix operating systems are highly optimized to transfer data from disk to network without copying data excessively.

Let's dive deeper to see how this is done.

First, we look at how Kafka sends a page of data on disk to the consumer

when zero copy is not used at all.

First, the data is loaded from disk to the OS cache.

Second, the data is copied from the OS cache into the Kafka application.

Third, the data is copied from Kafka to the socket buffer.

And fourth, the data is copied from the socket buffer to the network interface card buffer.

And finally, the data is sent over the network to the consumer.

Now this is clearly inefficient.

There are four copies and two system calls.

Now let's compare this to zero copy.

The first step is the same.

The data page is loaded from the disk to the OS cache.

With zero copy, the Kafka application uses a system call called send file to

tell the operating system to directly copy the data from the OS cache to the network interface card buffer.

In this optimized path, the only copy is from the OS cache into the network card buffer.

With a modern network card, this copying is done with DMA.

DMA stands for Direct Memory Access.

When DMA is used, the CPU is not involved, making it even more efficient.

To recap, sequential I.O and zero copy principle are the cornerstone to Kafka's high performance.

Kafka uses other techniques to squeeze every ounce of performance of modern hardware, but these two are the most important in our view.

If you'd like to learn more about system design, check out our books and weekly newsletter.

Please subscribe if you learned something new.

Thank you so much and we'll see you next time.

Baixar aplicativo

Tudo o que você precisa para falar fluentemente

Pronúncia com IANota em cada frase

Prática de IPADomine cada som

VocabulárioMonte seu banco de palavras

Jogo de vocabulárioAprenda brincando

Escaneie o QR

Download on theApp Store Get it onGoogle Play

Mesmo canal

FOR YOU

Vídeo recomendado

120 frases

Learn Data Modeling in 8 minutes: Dimensional Data Modeling, Data Vault, and One Big Table

Business EnglishUniversity StudentsWorking Adults

227 frases

Psychology of Intelligence: Learn Anything So Fast It's Almost Unfair

Business EnglishUniversity StudentsWorking Adults

32 frases

Rust in 100 Seconds

Business EnglishUniversity StudentsWorking Adults

42 frases

System Design: How to Build an API Rate Limiter

Business EnglishUniversity StudentsWorking Adults

243 frases

Proximity Search & Geospatial Indexes Explained

Business EnglishUniversity StudentsWorking Adults

11 frases

What are Design Patterns? | Introduction to Design Patterns and Principles | Geekific

Business EnglishUniversity StudentsWorking Adults

80 frases

The Most Confused Concepts in Engineering

Business EnglishUniversity StudentsWorking Adults

96 frases

Build a Real-Time Leaderboard on AWS with DynamoDB

Business EnglishUniversity StudentsWorking Adults

356 frases

Concurrency in Low-level Design Interviews w/ Staff Engineer

Business EnglishInterview EnglishUniversity Students

195 frases

JavaScript Visualized - Event Loop, Web APIs, (Micro)task Queue

Business EnglishUniversity StudentsWorking Adults

O que é a Técnica de Shadowing?

Shadowing é uma técnica de aprendizado de idiomas com base científica, originalmente desenvolvida para o treinamento de intérpretes profissionais. O método é simples, mas poderoso: você ouve áudio em inglês nativo e repete imediatamente em voz alta — como uma sombra seguindo o falante com 1-2 segundos de atraso. Pesquisas mostram melhora significativa na precisão da pronúncia, entonação, ritmo, sons conectados, compreensão auditiva e fluência na fala.

Técnica de shadowing: leia o guia completo passo a passo →

Prática de Shadowing: System Design: Why is Kafka fast? - Aprenda a falar inglês com vídeo

Escolha um modo de prática

Baixar aplicativo

Mesmo canal

Top 5 Redis Use Cases

The Secret Sauce Behind NoSQL: LSM Tree

Proxy vs Reverse Proxy (Real-world Examples)

Cache Systems Every Developer Should Know

System Design Was HARD - Until You Knew the Trade-Offs

8 Most Important System Design Concepts You Should Know

Everything You Need to Know About DNS: Crash Course System Design #4

CAP Theorem Simplified

What Is REST API? Examples And How To Use It: Crash Course System Design #3

System Design: Why is Kafka Popular?

What Are Microservices Really All About? (And When Not To Use It)

What is API Gateway?

10+ Key Memory & Storage Systems: Crash Course System Design #5

What Is Redis Really About? Why Is It So Popular?

Kubernetes Explained in 6 Minutes | k8s Architecture

How Does a URL Shortener Work?

How Git Works: Explained in 4 Minutes

Vídeo recomendado

Learn Data Modeling in 8 minutes: Dimensional Data Modeling, Data Vault, and One Big Table

Psychology of Intelligence: Learn Anything So Fast It's Almost Unfair

Rust in 100 Seconds

System Design: How to Build an API Rate Limiter

Proximity Search & Geospatial Indexes Explained

What are Design Patterns? | Introduction to Design Patterns and Principles | Geekific

The Most Confused Concepts in Engineering

Build a Real-Time Leaderboard on AWS with DynamoDB

Concurrency in Low-level Design Interviews w/ Staff Engineer

JavaScript Visualized - Event Loop, Web APIs, (Micro)task Queue

Sobre esta lição

Vocabulário e frases chave

Dicas de prática (shadowing)

O que é a Técnica de Shadowing?