Azure Event Hubs is a highly scalable data streaming platform and event ingestion service capable of receiving and processing millions of events per second. Event Hubs can process and store events, data, or telemetry produced by distributed software and devices. Data sent to an event hub can be transformed and stored using any real-time analytics provider or batching/storage adapters. With the ability to provide publish-subscribe capabilities with low latency and at massive scale, Event Hubs serves as the "on ramp" for Big Data.
Why use Event Hubs?
Event Hubs event and telemetry handling capabilities make it especially useful for:
- Application instrumentation
- User experience or workflow processing
- Internet of Things (IoT) scenarios
For example, Event Hubs enables behavior tracking in mobile apps, traffic information from web farms, in-game event capture in console games, or telemetry collected from industrial machines, connected vehicles, or other devices.
Azure Event Hubs overview
The common role that Event Hubs plays in solution architectures is the "front door" for an event pipeline, often called an event ingestor. An event ingestor is a component or service that sits between event publishers and event consumers to decouple the production of an event stream from the consumption of those events. The following figure depicts this architecture:
Event Hubs provides message stream handling capability but has characteristics that are different from traditional enterprise messaging. Event Hubs capabilities are built around high throughput and event processing scenarios. As such, Event Hubs is different from Azure Service Bus messaging, and does not implement some of the capabilities that are available for Service Bus messaging entities, such as topics.
Event Hubs features
Event Hubs contains the following key elements:
- Event producers/publishers: An entity that sends data to an event hub. An event is published via AMQP 1.0 or HTTPS.
- Partitions: Enables each consumer to only read a specific subset, or partition, of the event stream.
- SAS tokens: used to identify and authenticate the event publisher.
- Event consumers: An entity that reads event data from an event hub. Event consumers connect via AMQP 1.0.
- Consumer groups: Provides each multiple consuming application with a separate view of the event stream, enabling those consumers to act independently.
- Throughput units: Pre-purchased units of capacity. A single partition has a maximum scale of one throughput unit.
For technical details about these and other Event Hubs features, see the Event Hubs features overview.
For detailed Event Hubs pricing information, see Event Hubs Pricing.
For more information about Event Hubs, visit the following links: