New: Cookbooks and AI ExplanationsStep-by-Step recipes to solve problems connected to Roadmaps and Cheat Sheets. Need more details? Use AI buttons for structured and simple explanations with concrete examples throughout the whole platform.Take a look
12 recipes Β· 80 steps Β· about 65 minutes of reading
You've never actually sent a message.
Your producer call returns instantly, so you assume the message made it, until a broker blip proves you wrong.
A crash mid-batch. Did it save, or reprocess?
Two updates for the same order arrive out of order downstream, and support wants to know why.
Someone on the team asks how many partitions the new topic needs, and you're about to just copy the number from another team's topic without checking it.
Consumers keep dropping out and rejoining, throughput craters, and nobody touched the code.
Why did the whole partition stop moving over one bad row?
Nobody can agree whether the new topic should keep seven days of history or just the latest value per key.
A field type changed in last week's release, and three downstream consumers threw parsing errors at 2am.
The finance pipeline is double-counting some events after every consumer restart. 'Just dedupe it downstream' worked for a while, but it isn't cutting it anymore.
The dashboard shows yesterday's numbers, and the business wants today's, updating as events arrive.
You already know PySpark, and hand-writing the same aggregation logic again as a raw Kafka consumer feels like starting over.
Cookbook badge
Finish all 12 recipes to earn this.