Acknowledgment strategy
An acknowledgment strategy is a producer-side policy determining when a published message is acknowledged and what delivery guarantee applies.
Apache Kafka in Action
An acknowledgment strategy is a Kafka producer policy or setting that determines when a broker acknowledges a published message.
- How it is used
- Sets when a Kafka producer receives confirmation of a published message, balancing reliability against latency and performance.
- How deep it goes
- Explains all three ACK modes and tests insufficient replicas, then relates acknowledgments to producer timeouts and retries.
- Examples
- Demonstrates console-producer settings for three ACK modes and a broker-shutdown test that produces `NOT_ENOUGH_REPLICAS`.
- What you can do after
- Operate/configure it with `kafka-console-producer.sh`, and diagnose acknowledgment failures when too few replicas remain in sync.
Read how Apache Kafka in Action explains acknowledgment strategy →
Kafka for Architects
An acknowledgment strategy is a producer-side policy that determines when a Kafka record send is considered successful and what delivery guarantee applies.
- How it is used
- Guides producer configuration by balancing acknowledgment latency, replication durability, and business criticality.
- How deep it goes
- Explains all three acks modes and connects acks=all to replication, idempotence, retries, and ordering.
- Examples
- Uses a Customer 360 profile-update binding configured with acks=all.
- What you can do after
- Operate/configure Kafka producers with an acknowledgment level matched to durability, latency, and duplicate-prevention requirements.
Read how Kafka for Architects explains acknowledgment strategy →
Related concepts
- in-sync replicauses · An in-sync replica is a Kafka partition replica sufficiently caught up with its leader to remain eligible for failover.
- Kafka producerconfigured by · A Kafka producer is an application or client that publishes records to Kafka topics.
- all acknowledgmentincludes · All acknowledgment is a Kafka producer setting requiring confirmation from all in-sync replicas before a record write is considered successful.
- min.insync.replicasconfigured by · min.insync.replicas is a Kafka setting specifying the minimum number of in-sync replicas that must acknowledge a write for it to succeed.
- durabilitycontrasts with · Durability is the capacity of data, systems, or other artifacts to persist or remain usable over time despite failures or change.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.