System design · Key technologies: the tools you will actually name

Kafka and event streams: a log, not a queue

Kafka is a replicated, partitioned, append-only log that consumers read at their own pace, and nearly every design question about it (ordering, scaling, durability, replay) is really a question about partitions and offsets.

24 min read Full lesson in the app Patterns: partition-key, consumer-group, transactional-outbox, change-data-capture

What you'll be able to do

Before this: queues-and-backpressure, replication-and-consistency

Log in to read the rest of this lesson

Kafka is a replicated, partitioned, append-only log that consumers read at their own pace, and nearly every design question about it (ordering, scaling, durability, replay) is really a question about partitions and offsets. This walkthrough runs about 24 minutes, with runnable code you can edit and re-run as you read. A new account gets 7 days of Pro free, no card required.

Log in to continue

The first module of every track is free to read on the web: see what's open in System design.