✳flâneur — a map of the web's best reading

Exactly-once Semantics is Possible: Here's How Apache Kafka Does it

confluent.io · 4,849 words · saved by 1 readers

Wherever you are in your data streaming journey, you'll find the explainer videos and tutorials you need to advance your skills here. Learn more about our pricing structure, features and deployment options Compare your savings with Confluent to a self-managed Kafka deployment Use cases Clean and govern data at the source and turn topics into Iceberg or Delta Lake tables Build RAG and agentic AI use cases with real-time, contextual and trustworthy data Learn to build event-driven microservices applications with data streaming Discover best practices for common data streaming use cases Industries How to build and scale real-time AI agents with a data streaming platform General Resources Browse whitepapers, ebooks, reports & more Best practices, industry trends and news Browse on-demand or upcoming sessions Get up to speed on data streaming concepts Ensure successful outcomes with advisory and implementation services Developer Resources Courses, tutorials and language guides Guides, tutor

Exactly-once Semantics is Possible: Here's How Apache Kafka Does it New in Confluent Cloud: Making Data & Pipelines Accessible for AI-Ready Streaming | Learn More Login Contact Sales This post was originally published in 2017 and last updated March 2025. I’m thrilled that we have hit an exciting milestone the Apache Kafka ® community has long been waiting for: we have introduced exactly-once semantics in Kafka in the 0.11 release and Confluent Platform 3.3 . In this post, I’d like to tell you what Kafka’s exactly-once semantics mean, why it is a hard problem, and how the new idempotence a

Explore this link on the map →

related reading