
Apache Kafka — The Distributed Log, End to End
Apache Kafka runs the event backbone of a huge fraction of modern systems…
Tag
24 posts
Apache Kafka runs the event backbone of a huge fraction of modern systems…
We’ve built Kafka up from the log to production. The last and most valuable…
A Kafka cluster that’s been designed well (good keys, right durability, sensible…
A log of events is only half the story; the value is in processing it…
Everything so far has been the Kafka broker — the distributed log that stores…
So far we’ve treated “Kafka” as a thing that stores partitions and replicates…
Kafka’s superpower — retaining and replaying events — has a physical cost: all…
Lesson 5 said at-least-once “never loses data” — but why doesn’t it? Because…
“Does Kafka deliver each message exactly once?” is the question everyone asks…
Producers append; consumers read. But the clever part of Kafka consumption isn’t…
Before any configuration or API, the single most important thing to understand…
Lesson 1 said Kafka is a log. This lesson is the data model that turns “a log…
Events get into Kafka through a producer — a client that appends messages to a…
Every company that runs on data has an invisible layer of engineering underneath…
When a use case genuinely needs low latency (Lesson 2), you reach for streaming…
Every company I’ve worked with has had at least one “duplicate” incident from a…
Open Spotify and every interaction — pressing play, skipping a track, liking a…
Most of what a Slack message triggers does not happen in the request that sent…
Your data lives in a database, but that is rarely the only place it needs to be…
“I’ll use Kafka” is not an answer. “This needs a durable, replayable log to…
“Design the system behind an advertising dashboard” is a favourite analytics…
Most of the designs so far store data and answer queries against it. Stream…
A message queue decouples producers from consumers: services publish events…
Every system starts synchronous. User clicks a button, server does the work…

