azure-eventhub-dotnet

Topics in the source

• Azure.Messaging.EventHubs (.NET)
• Installation
• Environment Variables
• Authentication
• Client Types
• Core Workflow
• 1. Send Events (Batch)
• 2. Send Events (Buffered - High Volume)

High-throughput event streaming SDK for sending and receiving events via Azure Event Hubs. Current Versions: Azure.Messaging.EventHubs v5.12.2, Azure.Messaging.EventHubs.Processor v5.12.2 Required RBAC Roles: Sending: Azure Event Hubs Data Sender Receiving: Azure Event Hubs Data Receiver Both: Azure Event Hubs Data Owner | Client | Purpose | When to Use | |--------|---------|-------------| | EventHubProducerClient | Send events immediately in batches | Real-time sending, full control over batching | | EventHubBufferedProducerClient | Automatic batching with background sending | High-volume, fire-and-forget scenarios | | EventHubConsumerClient | Simple event reading | Prototyping only, NOT for production | | EventProcessorClient | Production event processing | Always use this for receiving in production | Control where to start reading: 1. Use EventProcessorClient for receiving — Never use EventHubConsumerClient in production 2. Checkpoint strategically — After N events or time interval, not every event 3. Use partition keys — For ordering guarantees within a partition 4. Reuse clients — Create once, use as singleton (thread-safe) 5. Use await using — Ensures proper disposal 6. Hand

This is an excerpt. Refer to the complete source and its current requirements.