Window Azure servicebus Messaging Message Queuing Technology Series 1-Basic concepts and architecture

The previous time studied the window Azure servicebus Messaging Message Queuing technology, has done a lot of technical research and code validation, recently prepared to summarize, share to everyone.

First, Windows Azure provides two types of Message Queuing mechanisms: Azure Queues and Servicebus Queues.

Among them, Azure Queues, as part of the azure storage infrastructure, provides a simple set of rest-based interface that provide reliable, persistent Message Queuing for different services .

Servicebus queues, as part of the Azure messaging infrastructure, supports both the queue and the publish subscription model, supporting WebService and integration modes .

This series mainly introduces Servicebus Queues. For the comparison of the selection of the two, you can refer to:

https://azure.microsoft.com/zh-cn/documentation/articles/service-bus-azure-and-service-bus-queues-compared-contrasted

Service Bus supports two different message modes:relayed messaging and brokered messaging. That is, the relay message pattern and the proxy message pattern.

Relay Message Mode relayed messaging, the biggest feature is: Send and receive messages require both the server and the client online, does not support the asynchronous mode.

Message processing process:

When the client sends a request to servicebus,azure, the load Balancer routes the request to any one of the network joint points (Gateway Nodes). If the request is a listener class request, the mesh joint point creates a new
Relay (Relay). If the request is a request to connect to the specified relay (Relay), the request is diverted to the gateway point of the specified trunk, which sends a rendezvous request to the listening client, requiring the listener client to create a temporary channel to receive the message. When the relay connection is established,

The client can exchange messages with the gateway node through the network joint point.

Proxy message Mode borkered messaging: Asynchronous, decoupled, message sender (Producer) and consumer (Consumer) do not need to be online at the same time, the message is stored in broker (proxy), waiting for the message consumer to process. Its core components include: queue, subject (TOPIC), publish subscription, and so on.

Message processing process:

When the client sends a request to servicebus,azure, the load Balancer routes the request to any one of the network joint points (Gateway Nodes). If the request contains a message entity (queue, subject, subscription), the Gateway node is first located in the Gateways store to locate the message store to which the message entity should be stored (message Store) and the message store corresponding message broker node (Messaging Broker), then sends the message to the specified message broker node, which processes the request, stores the message, and updates the Message entity State (delivered). The message Broker node sends a response back to the network node where the request is located, and then returns the client to the request.

Proxy message Mode borkered messaging is one of the most common common message patterns, supported by the industry's ACTIVEMQ, RABBITMQ and other message middleware, and is the focus of our further research.

Window Azure servicebus Messaging Message Queuing Technology Series 1-basic concepts and architecture