Microsoft releases the latest Event Hubs Clients to general availability. This means that the new libraries are now ready for production and it is completely supported by Microsoft.
What new libraries are available?
Consistent with their past design decisions, Microsoft is releasing two new NuGet packages, as per the
official blog.
- Microsoft.Azure.EventHubs: This library comprises the Event Hubs specific functionality that is currently found in the WindowsAzure.ServiceBus library. In here, you will be able to do things like send and receive events from an Event Hub.
- Microsoft.Azure.EventHubs.Processor: Replaces functionality of the Microsoft.Azure.ServiceBus.EventProcessorHost library. This is the easiest way to receive events from an Event Hub, and keeps you from having to remember things such as offsets and partition information between receivers.
Major Benefits of the new libraries
These new libraries come with three major benefits. They are the following, as per the official blog:
- Runtime portability: Using .NET Standard, it now comes with the ability to write a single code base which is portable across different .NET runtimes, which includes .NET Core, .NET framework, and the Universal Windows Platform. You can take this library and run it on Windows Server with .NET Framework 4.6, or on a Mac/Linux machine using .NET Core.
- Open source: The new libraries are open source and available on GitHub. The company states, “We love the interactions that we have with our customers, whether it be an issue or pull request.”
- Event Hubs now has its own library: The Event Hubs and Service Bus have been seemingly joined in the past, the use cases between these two products are often times different. Earlier, you needed to download a Service Bus library in order to use Event Hubs. These new libraries are specific to Event Hubs.