Event Hubs as a data highway
1. Streaming data using Azure Event Hubs
In this video, you’ll explore Azure Event Hubs, how to integrate Event Grid with Event Hubs, and the advantages of using them together.2. Introduction to Event Hubs
Think of Event Hubs as a multi-lane motorway for data. Millions of tiny cars (events) stream in, and multiple lanes (partitions) keep traffic flowing so different consumers can process data in parallel without jams. A common use case is app telemetry or website clickstreams feeding real-time dashboards and analytics.3. Event Hubs overview
Azure Event Hubs is a fully managed, real-time data integration service. It’s built for streaming large volumes of data: telemetry, logs, and application events, making it ideal for big-data scenarios and analytics pipelines.4. Comparing Event Hubs to Event Grid
While Event Hubs and Event Grid work with events, the two service types serve different purposes. Event Grid powers event-driven architecture, where an event from one app triggers execution in another. Event Hubs focuses on collecting and streaming high-throughput event data for processing and analytics.5. How Event Hubs work at scale
Event Hubs can ingest millions of events per second and stores them temporarily in partitions. Downstream consumers, such as Azure Stream Analytics or Apache Spark, process these events for real-time analytics, visualization, or storage.6. Event Hubs work at scale
Partitions enable high throughput by letting events be processed in parallel. If a consumer hits a transient failure, it can replay from an offset within the retention window. Handy for apps running at scale!7. Integrating Event Hubs with Event Grid
So where does Event Grid fit? Event Grid complements Event Hubs by enabling event-driven workflows. While Event Hubs streams data, Event Grid handles discrete events and can route them to an Event Hub when you need buffering and analytics.8. Integrating Event Hubs with Event Grid
Why route from Event Grid to Event Hubs instead of directly to consumers? First, Event Grid is about orchestration, triggering and routing discrete events, whereas Event Hubs is about durable, high-throughput ingestion for analysis. Second, Event Hubs integrates seamlessly with analytics services like Azure Stream Analytics, Databricks, or Kafka-compatible tools for real-time processing. Third, Event Hubs provides buffering so data isn’t lost if a consumer is temporarily unavailable.9. Connecting Event Hubs consumers
Target services receive data from an Event Hub by acting as consumers that read from partitions. To connect, a client needs the Event Hubs namespace, the Event Hub name, and an access key.10. Advanced Event Hubs features
A few more features: checkpointing lets consumers resume from where they left off. You can process events in batches for throughput, or handle them one by one for low-latency scenarios.11. Let's practice!
Let's go ahead and see how these concepts work in practice.Create Your Free Account
or
By continuing, you accept our Terms of Use, our Privacy Policy and that your data is stored in the USA.