beginnerProducer & Consumer Internals
What does a Kafka producer's `acks` setting control, and what's the trade-off between `acks=1` and `acks=all`?
`acks` controls how many broker replicas must confirm they've written a message before the producer considers it 'sent successfully.' `acks=1` only waits for the partition leader (faster, but a message can be lost if the leader crashes before replicating), while `acks=all` waits for all in-sync replicas (slower, but the message survives a leader failure) — a classic throughput-vs-durability trade-off.
This is a Pro chapter
Sign in, then upgrade to Pro or Power to unlock this and the full Spring Ecosystem Mastery library.
What does a Kafka producer's `acks` setting control, and what's the trade-off between `acks=1` and `acks=all`?