You will learn how to
- Configure the Application to Use Service Bus
- How to Create a Queue
- How to Send Messages to a Queue
- How to Receive Messages from a Queue
- How to Handle Application Crashes and Unreadable Messages
Now that you’ve learned the basics of Service Bus queues, follow these links to learn more.
- See the MSDN Reference: Queues, Topics, and Subscriptions.
- What is Service Bus Queues & how this is different from the Service Bus Relay?
The Windows Azure Service Bus provides two comprehensive messaging solutions – one, through a centralized “relay” service running in the cloud that supports a variety of different transport protocols and Web services standards, including SOAP, WS-*, and REST. The client does not need a direct connection to the on-premises service nor does it need to know where the service resides, and the on-premises service does not need any inbound ports open on the firewall.
The second messaging solution, new in the latest release of the Service Bus, enables “brokered” messaging capabilities. These can be thought of as asynchronous, or decoupled messaging features that support publish-subscribe, temporal decoupling, and load balancing scenarios using the Service Bus messaging infrastructure. Decoupled communication has many advantages; for example, clients and servers can connect as needed and perform their operations in an asynchronous fashion.
- Service Bus Queue Messaging Tutorial: http://msdn.microsoft.com/en-us/library/windowsazure/hh367512.aspx
- Service Bus Relay Messaging Tutorial: http://msdn.microsoft.com/en-us/library/windowsazure/ee706736.aspx
- Windows Azure Service Bus
- Service Bus How To’s