Confluent Developer ft. Tim Berglund, Adi Polak & Viktor Gamov cover image

Ask Confluent #6: Kafka, Partitions, and Exactly Once ft. Jason Gustafson

Confluent Developer ft. Tim Berglund, Adi Polak & Viktor Gamov

00:00

The Importance of Read Committed Transactions

The default out of the box is what we call read uncommitted. And it's just like in a database, I do begin transaction, I produce a bunch of events, and then I commit or abort? Yeah, that's exactly right. On the consumption side, similar to databases, also we have in isolation level. So an isolation level basically describes the visibility for this transactional data. The downside is really about the additional latency. But from a throughput perspective, you can still get very good throughput.

Play episode from 10:54
Transcript

The AI-powered Podcast Player

Save insights by tapping your headphones, chat with episodes, discover the best highlights - and more!
App store bannerPlay store banner
Get the app