Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[azservicebus] Document best practices and considerations for the library #22644

Open
richardpark-msft opened this issue Mar 27, 2024 · 2 comments
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. needs-team-attention This issue needs attention from Azure service team or SDK team Service Bus

Comments

@richardpark-msft
Copy link
Member

This came up in #22629, where the original question (do you support retries) went into an interesting discussion when we looked at how they got there. The big piece that I think we're missing is some general discussion about what areas can be tuned, and how they work.

Some things I can think of:

  • Being aware of connection sharing
  • Being aware of which aspects of the SDK are safe to use in a multithreaded way (ie, all of it, but people might not think about it being beneficial)
  • Batching messages vs sending single messages
  • Tuning ReceiveMessages() calls - max wait time + max batch wait time
  • Retry policy tuning (our policy is very conservative)
@richardpark-msft richardpark-msft self-assigned this Mar 27, 2024
@richardpark-msft richardpark-msft added Service Bus Client This issue points to a problem in the data-plane of the library. labels Mar 27, 2024
Copy link

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @EldertGrootenboer @jfggdl.

@github-actions github-actions bot added needs-team-attention This issue needs attention from Azure service team or SDK team Service Attention This issue is responsible by Azure service team. labels Mar 27, 2024
@richardpark-msft richardpark-msft removed the Service Attention This issue is responsible by Azure service team. label Mar 27, 2024
@richardpark-msft
Copy link
Member Author

(@EldertGrootenboer , @jfggdl ) incorrect routing, no service attention required for this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Client This issue points to a problem in the data-plane of the library. needs-team-attention This issue needs attention from Azure service team or SDK team Service Bus
Projects
None yet
Development

No branches or pull requests

1 participant