1d:I[2890,["266","static/chunks/870fdd6f-4fcc92c129a57d11.js","970","static/chunks/970-91a3a37cc668faba.js","857","static/chunks/857-3b2a1421afa266d2.js","965","static/chunks/app/podcasts/episode/%5BpodcastEpisodeGuid%5D/page-e939c6b91b4a25d4.js"],"default"] 1e:I[1318,["266","static/chunks/870fdd6f-4fcc92c129a57d11.js","970","static/chunks/970-91a3a37cc668faba.js","857","static/chunks/857-3b2a1421afa266d2.js","965","static/chunks/app/podcasts/episode/%5BpodcastEpisodeGuid%5D/page-e939c6b91b4a25d4.js"],"default"] 1f:T564,

It has been said that in distributed messaging, there are two hard problems: 2) exactly once delivery, 1) guaranteed order of messages and 2) exactly once delivery. Apache Kafka® has offered exactly once processing since version 0.11, which allows properly configured producers and consumers to make the guarantee that each message will be processed exactly one time.

In this episode, Kafka Streams engineer Guozhang Wang walks through the implementation of transactional messaging in Kafka in some detail, including the idempotent producer API, the transaction coordinator responsible for managing the transaction log and consumer configurations. It’s a complex topic, but he takes us through it carefully and completely.

EPISODE LINKS

20:T8c2,

‌

Episode description

Diving into Exactly Once Semantics with Guozhang Wang

Episode description