Did the Kafka publication actually happen?
Separate local acceptance, acknowledgement, replicated visibility, and ambiguous caller outcomes.
←All Series
📡
Kafka Engineering
A source-guided course on Kafka protocol internals, platform ownership, KRaft and KIP-848 migrations, compatibility, portability, performance, and production failure boundaries.
complete13 / 13 episodes•176 min total•advanced
Series Progress100%
Start with the problem you have
You do not need to begin at chapter one. Follow a short path from the failure boundary to a practical decision.
Which offset may this consumer commit?
Compute the completed owned frontier, preserve real gaps, and reject stale completion.
Can this business operation happen twice?
Name the identity and smallest transaction that protects the actual sink effect.
What You'll Learn
- ✓Read and debug Kafka request framing and version negotiation
- ✓Trace producer, fetch, replication, compression, and quota behavior
- ✓Plan KRaft, KIP-848, and portability migrations without false equivalence
- ✓Define ownership boundaries between platform and application teams
- ✓Diagnose production failures from protocol and operational evidence
Episodes by Track
📡
Protocol Internals
Implementation, wire compatibility, request flow, durability, compression, and quotas
8 posts
🛠️
Production & Platform
Consumer-group ownership, platform contracts, observability, and operational boundaries
1 post
🚀
Evolution & Migrations
KRaft, KIP-848, compatibility, portability, and vendor transitions
4 posts
Prerequisites
- •Kafka fundamentals
- •Distributed systems fundamentals
- •Networking fundamentals
Who This Is For
- •backend-engineers
- •platform-engineers
- •kafka-operators
- •architects