1. Meet Kafka
1. Meet Kafka
Chapter 1 of Kafka: The Definitive Guide — 9 sections.
Source: Kafka: The Definitive Guide, 2nd Ed. (Shapira, Palino, Sivaram, Petty), Ch. 1 Learning goal for this chapter: understand why a log-shaped broker exists at all. Everything in later chapters (replication, exactly-once, Streams) is a consequence of the design decisions made here.
Sections
- 1.14What problem does Kafka solve?The problem is not "we need a queue." The problem is N×M point-to-point coupling in a data platform.
- 1.2Why wasn't something else enough?This is answered concretely by LinkedIn's history, which is the honest version of the story.
- 1.38How does it work internally? (the core object model)A message is the unit of data — think a DB row or record.
- 1.41Why Kafka? (the property-by-property case)Note the framing on platform features: these are not full platforms.
- 1.5Use cases (with the "why Kafka specifically" for each)The win: avoids duplicating this logic in every app, and enables aggregation that would not otherwise be possible (you can't batch a user's notifications if each app sends its own…
- 1.6Failure catalogWhat actually breaks in production (Ch. 1 foundations)Chapter 1 is conceptual, but it plants several landmines that detonate later.
- 1.71Deployment / monitoring / scaling / backup — what Ch. 1 establishesThese are covered properly in Ch. 2, 7, 10, 12, 13, but Ch. 1 sets the frame:
- 1.8Historical / trivia worth knowing
- 1.9Self-testSelf-test — can you answer these without looking?
Kafka: The Definitive Guide
Chapter-by-chapter notes on Kafka: The Definitive Guide — producers, consumers, internals, exactly-once semantics, operations, and stream processing.
1.1 What problem does Kafka solve?
The problem is not "we need a queue." The problem is N×M point-to-point coupling in a data platform.