Integrate Rust Apps with Azure Event Hubs

This skill uses the Azure Event Hubs SDK for Rust (azure_messaging_eventhubs plus azure_identity, installed via cargo add) to build against Event Hubs, Azure's big-data streaming and event-ingestion platform. It defines the core concepts: a namespace containing Event Hubs, an Event Hub as a partitioned event stream, a partition as an ordered sequence of events, and producer/consumer roles for sending and receiving. A ProducerClient is built with ProducerClient::builder().open(...) authenticated via DeveloperToolsCredential, and sends either a single event (send_event) or a batch (create_batch then try_add_event_data per event, checking its boolean return for capacity, followed by send_batch). A ConsumerClient is built the same way and opens a receiver scoped to a specific partition (open_partition_receiver), then pulls a bounded number of events (receive_events) and reads each event's body. Event Hub-level and partition-level metadata (partition IDs, last enqueued sequence number) can be queried directly from the consumer client. Best practices: reuse client instances across many sends rather than recreating them, prefer batches over individual sends for efficiency, check try_add_event_data's return value for batch capacity, process partitions in parallel since each is independently consumable, use consumer groups to isolate different consuming applications, and add the companion azure_messaging_eventhubs_checkpointstore_blob crate for checkpointing in distributed consumer scenarios.

Use this skill when building a Rust application that sends to or reads from Azure Event Hubs - event ingestion, streaming telemetry, or partitioned event processing. It is not a guide to distributed, load-balanced consumption with automatic checkpointing across many consumer instances - that requires the separate checkpoint-store crate and its own coordination logic, only briefly referenced here as an add-on rather than demonstrated.

Input is raw event byte payloads to send, or a partition ID and event count to receive from. Output is send confirmations, received events (with their body), and Event Hub/partition metadata (partition IDs, sequence numbers).

Built on the Azure Event Hubs Rust SDK (azure_messaging_eventhubs), authenticated via Azure Identity's DeveloperToolsCredential, with an optional companion crate (azure_messaging_eventhubs_checkpointstore_blob) for checkpointing against Azure Blob Storage.

cargo add azure_messaging_eventhubs azure_identity

Rust developers building event-ingestion or streaming applications on Azure Event Hubs who need to send and receive partitioned events without hand-rolling the AMQP protocol themselves.