Skip to content

Commit 4fc7e52

Browse files
committed
idempotency support
1 parent c4f263b commit 4fc7e52

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

articles/event-hubs/event-hubs-for-kafka-ecosystem-overview.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Use event hub from Apache Kafka app - Azure Event Hubs | Microsoft Docs
33
description: This article provides information on Apache Kafka support by Azure Event Hubs.
44
ms.topic: overview
5-
ms.date: 06/27/2022
5+
ms.date: 10/14/2022
66
---
77

88
# Use Azure Event Hubs from Apache Kafka applications
@@ -96,6 +96,12 @@ The Event Hubs for Apache Kafka feature is one of three protocols concurrently a
9696

9797
Additionally, Event Hubs features such as [Capture](event-hubs-capture-overview.md), which enables extremely cost efficient long-term archival via Azure Blob Storage and Azure Data Lake Storage, and [Geo Disaster-Recovery](event-hubs-geo-dr.md) also work with the Event Hubs for Kafka feature.
9898

99+
## Idempotency
100+
101+
Event Hubs for Apache Kafka supports both idempotent producers and idempotent consumers.
102+
103+
One of the core tenets of Azure Event Hubs is the concept of **at-least once** delivery. This approach ensures that events will always be delivered. It also means that events can be received more than once, even repeatedly, by consumers such as a function. For this reason, it's important that the consumer supports the [idempotent consumer](https://microservices.io/patterns/communication-style/idempotent-consumer.html) pattern.
104+
99105
## Apache Kafka feature differences
100106

101107
The goal of Event Hubs for Apache Kafka is to provide access to Azure Event Hubs capabilities to applications that are locked into the Apache Kafka API and would otherwise have to be backed by an Apache Kafka cluster.

0 commit comments

Comments
 (0)