Azure-docs: Confusing documentation re library versions

[ericsampson]

This page, and really all the SB documentation, needs to be scrubbed so that it only refers to concepts/code in the new Microsoft.Azure.ServiceBus library. Or if it's going to cover both old and new libraries, then it needs to be very clear which examples/code are specific to each. Right now the documentation is very confusing. Thanks!

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: f7eb26ad-3f91-13f4-5827-9dd398412f9d
• Version Independent ID: 1e3dc2ac-1d5e-3da1-7d51-91d36bda14f2
• Content: Best practices for improving performance using Azure Service Bus
• Content Source: articles/service-bus-messaging/service-bus-performance-improvements.md
• Service: service-bus-messaging
• GitHub Login: @axisc
• Microsoft Alias: aschhab

[mike-urnun-msft]

Hi @ericsampson - Thank you for your feedback! We have assigned this issue to the author to review further and take the right course of action.

[peheje]

I am using Microsoft.Azure.ServiceBus, and I had no idea what you meant by

"Service Bus client objects, such as QueueClient or MessageSender, are created through a MessagingFactory object"

So when using Microsoft.Azure.ServiceBus in an ASP.NET application, how often should I call "new QueueClient" with the connection string? Is there a way I can reuse the connection?

[peheje]

The QueueClient has a connection you can pass to it, I'm guessing this can be reused. I ended up setting up our Dependency Injection library to keep a pooled list of initialized QueueClients.

[emily-curry]

Does this same concept apply to service bus libraries in other languages? Since this article is in the "Concepts" section I assume the advice is platform-agnostic, but so many references are made to .NET code that it's difficult to tell whether these suggestions apply to other client libraries.

[jigneshjdesai]

Very confusing indeed. I am trying to use this in production with new Microsoft.Azure.ServiceBus library and am struggling to decide how should I be creating connections or creating clients.

[davidallyoung]

I would like to add in here, being a consumer of the Microsoft.Azure.Servicebus library, I'm really left out of the loop on how to achieve some of these performance recommendations.

I'd like to point anyone looking for BASIC samples to go here: https://github.com/Azure/azure-service-bus/tree/master/samples/DotNet/Microsoft.Azure.ServiceBus

However, these samples do not get into the high-throughput recommendations made here like settings the batch interval, etc. So far I can't see that these options are exposed, and if they are they're not well enough exposed to a consumer of the API to discover it for themselves. If they're not going to exposed plainly, we should get documentation updated somewhere for these performance recommendations in the new library.

[ericsampson]

This was just updated by @IEvangelist, check it out.

[IEvangelist]

Hi @ericsampson,

I hope all is well, we've made changes to the doc to address your expressed concern. Please have a look again at the article and let me know if these are satisfactory enough to close this issue.

Merged here, updates to the doc are live here.

[peheje]

Wow This is really nice!

I guess I need to go back and refactor a bit according to these recommendations.

[davidallyoung]

This is great, thank you for updating this!