Hello Kafka — topic, brokers, records
A topic is a named partitioned log spread across brokers in a cluster; producers send records (key, value, timestamp, headers) to a topic and consumers poll records back — every later scene zooms into one slice of this picture.
You've named the parts. Now meet a real topic — partitioned across brokers — and watch a record's journey from producer call to consumer poll, end to end.
Scene 01a
Hello Kafka — topic, brokers, records
- Watch
- Try it
- Predict
- Capture
A topic called "events" lives on a broker as a partitioned log. The producer sends records into Partition 0; the consumer polls them back. Watch the code panel — the line that's running glows.
Where this sits in Build Kafka
Scene 01a of 13, in the Why a log? act — Orientation — the log is the database, not a queue.. Foundations: what's a topic vs a partition, what's a broker, what does the producer/consumer code actually look like.
Up next. The log is the database — why a Kafka log isn't a queue, and why that one fact unlocks every later scene in the curriculum.
Designs that use this
- Twitter / X TimelinePush or pull? Both. The canonical fanout problem.
- Uber / Lyft — Match Drivers and RidersMatch a rider to the closest acceptable driver in under 3 s. Geohash, S2, surge.
- Slack / DiscordChannels and history. Push or pull — and how a hot-channel fanout doesn't melt the gateway.
- WhatsApp / MessengerHundreds of millions of long-lived sockets, sub-second 1:1 + group delivery, E2E-encrypted, multi-device, multi-region active-active.