How to optimize bandwidth when sending to EventHubs using .Net core application

How to create multiple EventHubClients that use several basic TCP connections to provide fast write to EventHubs from a .net web application?

The programming guide for EventHubs ( https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-programming-guide ) says:

It is important to note that additional EventHubClient objects created from the factory messaging instance reuse the same underlying TCP connection. Therefore, these objects have a bandwidth limit on the client side. The Create method reuses one factory messaging. If you need very high throughput from a single sender, you can create multiple messages and one EventHubClient object from each factory message.

And then they have a code sample:

var factory = MessagingFactory.CreateFromConnectionString("your_connection_string");
var client = factory.CreateEventHubClient("MyEventHub");

However, I do not know where / if there is a MessagingFactory in the .Net kernel? Is it possible to do this from the .Net kernel? I looked at Microsoft.Azure.ServiceBus but could not find.

+4
source share
1 answer

, EventHubClient.CreateFromConnectionString EventHubs , . ( TCP- Windows Resource Monitor).

( , , EventHubClients, MessaginFactory, , . , - , )

+1

Source: https://habr.com/ru/post/1690613/


All Articles