Up to date with Kafka 4
Most material I found still shows ZooKeeper. This one starts with KRaft and the official Docker image, which saved me time.
Browse
Topics, partitions, producers and consumers in KRaft mode, delivery guarantees, schemas and Kafka Connect, with Python examples
Created by Priya Raghavan
Kafka sits underneath a huge share of modern data platforms. It is also easy to use badly: lost messages, duplicate processing, consumers that fall hours behind. This course teaches how Kafka really works so you can make it reliable.
We use Apache Kafka 4, which runs only in KRaft mode. ZooKeeper is gone, so the setup is simpler than older tutorials suggest, and some old advice no longer applies.
Section one is written in full and gets Kafka running on your laptop with the official Apache Docker image. Later sections are videos built around one scenario: order events from a web application flowing to a warehouse and to a real time dashboard. Code examples use Python with the confluent-kafka client, and every concept maps directly to Java, Go or any other client library.
Streaming and data platform engineer. Kafka, Python pipelines and DuckDB explained plainly
I work on data platforms where events arrive all day and someone always wants yesterday's numbers fixed. Most of my time goes into Kafka topics, Python ingestion services and the small analytical tools that make debugging them faster.
I started teaching because new data engineers kept asking me the same questions: why is this consumer lagging, why did this file load twice, why is this query slow. My courses answer those questions with small, complete examples rather than slides.
Outside work I maintain a few open source notebooks for teaching SQL over Parquet files, and I like explaining file formats more than I probably should.
Most material I found still shows ZooKeeper. This one starts with KRaft and the official Docker image, which saved me time.
The partition and offset lesson plus reading kafka-consumer-groups output made lag finally make sense to me.
The idea of effectively once through idempotent writes rather than chasing exactly once everywhere was the key insight for our team.
We needed CDC from PostgreSQL and the Debezium lesson got us running in an afternoon, including how deletes and tombstones work.
The broker failure experiments showed exactly when acks=1 loses data. Schema section could use one more worked example.
Assumes you know Python, which suited me. The dead letter topic pattern is now in our pipeline.
Accurate and thorough, but the rebalance lesson moved quickly. I had to rewatch it twice.