⚡ Free course
Streaming & Kafka
Reason about events, ordering and lag the way a platform team does.
What you will learn
- CDC with Debezium: reading the database log instead of the database
Polling a production database every five minutes is how analytics teams get their access revoked. CDC reads the log the database already writes — and gets every change, in order, including the deletes. - Kafka hands-on: your first producer and consumer
Twenty minutes from nothing to watching your own events flow. Concepts stick once you have broken something yourself. - Events and the Log — the Kafka mental model
Kafka is not a queue. It is an append-only log that many readers can read at their own speed. - Choosing a Partition Key
The partition key decides two things at once: what stays ordered, and what gets overloaded. - Consumer groups, rebalancing and offsets
Three mechanisms decide whether your consumer loses data, duplicates it, or quietly stops: where the offset is committed, when the group rebalances, and how long a slow poll is tolerated. - Producer guarantees: acks, retries, idempotent producers (coming soon)
- Schema registry: Avro, Protobuf, compatibility (coming soon)
- Spark Structured Streaming vs Flink (coming soon)
- Windowing and joins on streams (coming soon)
- Kafka Connect and CDC with Debezium (coming soon)
How the course works
- Each chapter is a short book: the basics, the explanation in several ways, the words to know, and a two-minute summary.
- Then you test yourself — quiz, puzzles — and recall it on two different days, so it stays.
- Blinks (one idea per screen), games and a daily plan keep you coming back. It is free.