How deeply does Apache Kafka in Action cover leader-follower replication model?

Explains producer flow, follower fetching, offsets, controller failover, recovery, and preferred leader election.

Leader-follower replication model

The leader-follower principle assigns one replica as the leader that handles coordination and other replicas as followers that copy its data.

A leader coordinates one partition’s replicas: producers send records to it, while followers fetch the log and report their offsets. Followers stay current so an in-sync replica can take over when the leader fails. section 5.3

A Kafka replication flow makes the operational trade-offs visible:

Distribute partition leadership across brokers to balance coordination and write load. section 5.3
Let followers fetch records and expose their offsets so acknowledgments can reflect replica progress. section 5.3

Three-broker product-price topic

A topic with three partitions and replication factor three places every partition on all three brokers while spreading leaders across them. Stopping Broker 3 moves Partition 1’s leadership to Broker 1; restarting Broker 3 restores synchronization, and preferred leader election can return leadership to Broker 3.

How Apache Kafka in Action covers it

liveBook manning.com

Read Apache Kafka in Action on liveBook Get the book at manning.com

Related concepts

replicauses · A replica is a copy of data or state, or an equivalent running instance of a component, maintained alongside others in a replicated system.
Apache Kafkaused by · Apache Kafka is a distributed event-streaming platform for publishing, storing, processing, and consuming streams of records.
databaseused by · A database is an organized collection of persistent data managed by software for storage, retrieval, querying, and modification.
SQLconfigures · SQL is a standardized declarative language for defining, querying, and manipulating data and structures in relational database systems.
consistencycontrasts with · Consistency is the property of related data, behavior, outputs, or states agreeing with one another or conforming to defined rules across relevant instances or operations.

This explainer was generated by Manning's knowledge graph from the text of Apache Kafka in Action. The section links point to the parts of the book it draws on.