What’s in This Chapter
- Understanding the Service Bus
- Programming Service Bus brokered messaging
- Selecting between REST and managed clients
- Choosing between Service Bus Brokered Messaging and Windows Azure Queues
An important component of any cloud architecture is the means by which the various components communicate. This chapter examines the September 2011 Release of the Service Bus, a cloud-hosted platform designed to enable on-premises to on-premises, cloud-hosted to cloud-hosted, and hybrid on-premises to cloud-hosted communication scenarios.
What Is Service Bus?
The Windows Azure Service Bus represents a rich collection of cloud-hosted services that enables both brokered and relayed communication scenarios. This section introduces the major features Service Bus provides.
Understanding Service Bus Brokered Messaging
Service Bus brokered messaging takes the basic concept of a hosted queue and extends it to provide support for:
- Publish-subscribe messaging: This is where one sender can broadcast messages to multiple interested recipients.
- Temporal decoupling: This is where recipients do not need to be online when senders transmit.
- Load leveling: A situation in which a spike of sent messages does not overwhelm recipients who see a constant stream of messages.
These features enable message-driven communication between managed and REST clients, both on-premises and cloud-hosted, so long as the Service Bus is accessible from the clients by TCP or outbound ...