When we consume a message, we need to decide when to acknowledge that we are done with it. Depending on our choice, we can end up with either an at-most-once, at-least-once, or exactly-once (effectively-once) delivery guarantee. Although an exactly-once guarantee is technically impossible, Kafka includes transactional semantics that can achieve an effectively-once guarantee. This video will discuss each of these delivery guarantees and show how you can implement them. It will also highlight the dangers of operating with the default auto-commit settings in .NET.
We will only share developer content and updates, including notifications when new content is added. We will never send you sales emails. 🙂 By subscribing, you understand we will process your personal information in accordance with our Privacy Statement.