Eksporter (0) Skriv ut
Vis alt
EN
Dette innholdet er ikke tilgjengelig på ditt språk, men her er den engelske versjonen.

Conclusion: Best Practices for Leveraging Azure Service Bus Brokered Messaging API

Updated: March 19, 2014

The cloud-based messaging and communication infrastructure supported by Microsoft Azure Service Bus includes reliable message queuing and durable publish/subscribe messaging capabilities. Because such “brokered” messaging services provided by Service Bus may be subject to quotas with respect to active concurrent connections maintained by messaging entities (such as a queue, topic or subscription), this article detailed some best practices in managing the specifics involved in the lifecycle of such entities and messaging objects, and provided guidance on building your applications with an awareness of resource efficacy.

Of equal importance, when building solutions that have dependencies on such cloud-based technologies, it’s important to build an element of reliability and resilience into your code, and this article has imparted guidance and some real-world examples on how to do so. Such robust practices help cloud-based applications deal with anomalies that may be out of your control, such as transient network communication errors that can manifest themselves in multi-tenant, cloud-based environments.

Finally, this article provided best practices to help you design code that is robust and efficient, while leveraging some of the advanced features of Service Bus, such as sending and receiving messages asynchronously, and implementing reliable message loops as part of that process.

Additional Resources/References

For more information on the topic discussed in this article, please refer to the following resources:

Fellesskapsinnhold

Legg til
Vis:
© 2014 Microsoft