azure-service-bus-dotnet
azure-service-bus-dotnet copied to clipboard
Document best practices for high-performance usage
I'd like to see some documentation on how to best use this library in high-performance scenarios. For example, given a web server that needs to send thousands of messages per minute spread among multiple queues and topics, what are the best practices? Which objects should be cached and reused and which should be recreated when needed? Will any of the clients ever end up in an error state and need to be recreated? Are there threading issues to be aware of with the clients?
Thank you and congrats on getting to 1.0
I'm also interested in best practice with regards to threading.
These docs https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-performance-improvements mention You can safely use the QueueClient object for sending messages from concurrent asynchronous operations and multiple threads. though this is of course for the old library, so it would be interesting to know if this holds (and possible have that article updated to reflect the state of this library where it differs).
Thanks, and also another congrats on 1.0!