หมายเหตุ
การเข้าถึงหน้านี้ต้องได้รับการอนุญาต คุณสามารถลอง ลงชื่อเข้าใช้หรือเปลี่ยนไดเรกทอรีได้
การเข้าถึงหน้านี้ต้องได้รับการอนุญาต คุณสามารถลองเปลี่ยนไดเรกทอรีได้
This article provides following information for the SDKs supported by Azure Event Hubs:
- Location of package that you can use in your applications
- GitHub location where you can find source code, samples, readme, change log, reported issues, and also raise new issues
- Links to quickstart tutorials
Client SDKs
The following table describes all the latest available Azure Event Hubs runtime clients. The core focus of these libraries is to send and receive messages from an event hub.
| Language | Package | Reference |
|---|---|---|
| . NET Standard | Azure.Messaging.EventHubs | |
| Azure.Messaging.EventHubs.Processor | ||
| Java | azure-messaging-eventhubs | |
| azure-messaging-eventhubs-checkpointstore-blob | ||
| Python | azure-eventhub | |
| azure-eventhub-checkpointstoreblob-aio | ||
| JavaScript | Azure/event-hubs | |
| azure/eventhubs-checkpointstore-blob | ||
| Go | Azure-event-hubs-go | |
| C | Azure-event-hubs-c |
The following table identifies older Azure Event Hubs runtime clients for existing applications. Use the current clients listed in the preceding table for development and migration.
Important
WindowsAzure.ServiceBus was retired for Event Hubs on September 30, 2026 and no longer receives official support or updates. Migrate Event Hubs applications to Azure.Messaging.EventHubs. For details, see the retirement announcement.
| Language | Package | Reference |
|---|---|---|
| . NET Standard | Microsoft.Azure.EventHubs (legacy) | |
| Microsoft.Azure.EventHubs.Processor (legacy) | ||
| . NET Framework | WindowsAzure.ServiceBus (retired) | Migrate to Azure.Messaging.EventHubs. |
| Java | azure-eventhubs (legacy) |
Management SDKs
Here's a list of currently available management-specific libraries. None of these libraries contain runtime operations, and are for the sole purpose of managing Event Hubs entities.
.NET packages
Client libraries
- Azure.Messaging.EventHubs: It's the current version of the library, conforming to the unified Azure SDK design guidelines and under active development for new features. It supports the .NET Standard platform, allowing it to be used by both the full .NET Framework and .NET Core. There's feature parity at a high level with Microsoft.Azure.EventHubs, with details and the client hierarchy taking a different form. This library is the one that we recommend you to use.
- Microsoft.Azure.EventHubs: It was the initial library to break out Event Hubs into a dedicated client that isn’t bundled with Service Bus. It supports the .NET Standard 2.0 platform, allowing it to be used by both the full .NET Framework and .NET Core. It's still the dominant version of the library with respect to usage and third-party blog entries, extensions, and such. The baseline functionality is the same as the current library, though there are some minor bits that one offers and the other doesn’t. It's currently receiving bug fixes and critical updates but is no longer receiving new features.
- WindowsAzure.ServiceBus: This retired .NET Framework library included both Event Hubs and Service Bus messaging APIs. Migrate Event Hubs applications to
Azure.Messaging.EventHubs.
Management libraries
- Microsoft.Azure.Management.EventHub: It's the current GA version of the management library for Event Hubs. It supports the .NET Standard 2.0 platform, allowing it to be used by both the full .NET Framework and .NET Core.
Next steps
You can learn more about Event Hubs by visiting the following links: