Azure Event Hubs are truly offering “hubs” for the Azure portal. This technology offers technology through which staggering amounts of data can be processed and then made available for analysis and/or storage. This data can come from a variety of sources, which can include websites, mobile devices and even machines.
Due to the fact that massive amounts of data can be received from devices and apps, many people are pointing to this new Microsoft service as being the perfect companion to the data from IoT, or Internet of Things. IoT data comes from a variety of devices and also arrives incredibly quickly and in massive numbers.
The impressive capabilities of Azure Event Hubs include logging millions of events per second. It also has nearly real time and event buffering. Users will receive high availability, with all the benefits of scalability and flexible throttling.
How Does Event Hubs Work?
The end goal is to analyze all the data that is produced by devices and apps. Messages are called “event data” and include metadata, the body of the event, as well as a property bag. This event data makes up the partitions. With Event Hubs, the end consumer will only read part of the message stream due to these partitions.
The event ingestor is designed to sit between producers of events and consumers of events. At the beginning of the pipeline, the Event Hub collects the data. Then once it is collected, an analytics provider or batching/storage adapter can then host it. Ultimately, the data can be separate from those events where it is stored. As a result, users can freely access the data.
With Event Hubs, there is a partitioned consumer pattern. Each consumer reads just a partition from the data stream. Users can create between 8-32 partitions when they create their Event Hub. These partitions help organize the data. This partition number cannot be changed after the Event Hub creation. When users set up their Event Hubs, they are encouraged to think long-term. Subscription rates are accessed through throughput units and ingress events, which are directly connected to usage. Basic as well as Standard plans are available.
How Does Service Bus Compare To Event Hubs?
When it comes to Microsoft services that handle messages from devices, many people think of Service Bus. Azure Event Hubs are different from Service Bus in a few key ways. First of all, Event Hubs are more for high throughput, and more for one-way event processing scenarios. While messaging abilities may be lacking in Event Hubs, they can be found in Service Bus. Therefore, Event Hubs should not be viewed as a messaging solution.
Why Consider Using Event Hubs?
Event Hubs are perfect for analyzing big data. This amount of data can be overwhelming and impossible to crunch, without a managed event service that has elastic scale capabilities. By the term “elastic,” we mean that it can handle spikes when they occur and it works with load profiles of different sizes.
What Event Hubs Can Be Used For:
-The Internet of Things
-Telemetry data from machines or vehicles
-In-Game Event Capture
Microsoft has aimed to make Events Hubs convenient with pluggable adapters that work with other cloud services, as well as flexible authorization. Users can also connect a variety of data sources. It’s even possible to maintain event order per device even when processing data from millions of devices.
Thanks to Event Hubs, huge amounts of incoming data no longer need to be an insurmountable hurdle. It is possible for companies to process high levels of data without setting up in-house solutions.
Post written by Jason Milgram, Director Software Development, Champion Solutions Group / MessageOps
Microsoft Azure MVP (2010-current)