Deep Dive Into Azure Service Bus

Prerequisites

• Microsoft Azure account.

Introduction to Azure Service Bus

An Azure Service Bus is a multi-tenant Cloud Service, which means that the Service is shared by the multiple users. Each user creates a namespace and defines the communication mechanism requirements within that namespace.

 

Image Source - Microsoft

Within an Azure Service Bus namespace, we can use one or more instances of four different communication mechanisms, each of which connects the Applications in a different way. A few elements of it are given below.

• Queues
  Queues allow one-directional communication and each queue acts as an intermediary that stores sent messages, until they are received. Each message is received by a single recipient.

• Topics
  Topics provide one-directional communication, using subscriptions- a single topic can have multiple subscriptions and its like a queue, a topic acts as a broker but each subscription can optionally use a filter to receive only messages that match specific conditions.
  
  
• Relays
  Relays provide bi-directional communication and unlike queues and topics, a relay doesn't store in-flight messages. It's not a broker, it just passes them on to the destination application.

Why do we need Azure Service Bus?

The purpose of this Service is to make the communication easier. When two or more business partners want to exchange the information, they need a communication mechanism. Service Bus is a brokered or third-party communication mechanism. Azure Service Bus is similar to a mailing Service in the physical world and make it very easy to send different types of letters and packages with a variety of delivery guarantees, anyplace in the world.
  
Similar to the mailing Service delivering letters, Azure Service Bus is flexible information delivery from both the sender and the recipient. The messaging Service confirms that the information is delivered even if the two parties are never both online at the same time or if they aren't available at the exact same time.

Advantages of Service Bus

• Simplify enterprise Cloud messaging.
• Build scalable Cloud solutions.
• Implement complex messaging Workflows.
• Service Bus Relay.
• Enable secure communication across hybrid Cloud solutions.
• Easily allow multiple apps to share one connection.

Create a Service namespace

Before using Service Bus queues in Azure, we must first create a namespace.

To create a namespace, follow the steps given below.

Step 1

Sign in to the online Microsoft Azure Portal,

Step 2

In the Jump bar, click New followed by clicking Enterprise Integration and then click Service Bus.

Step 3

In creating namespace account blade, enter a namespace name. The system immediately checks to see, if the name is available. After making sure the namespace name is available, choose the pricing tier (Basic, Standard or Premium).

 

Step 4

In the Subscription field, choose an Azure subscription in which you can create the namespace.

Step 5

In the Resource group field, choose an existing resource group in which the namespace will be live or create a new one.

Step 6

In Location, choose the country or the region in which our namespace should be hosted.

Step 7

Finally click Create button. The system now creates your namespace and enables it.

 

We might have to wait for several minutes as the system provisions resources for our account.

Summary

We have now created a Service Bus Messaging namespace.