Windows Azure - AppFabric Service Bus Application

The application requires the following activities:

  1. Creating the Namespace
  2. Create the Server and Deploying
  3. Create the Client and Test

We can now start with the activities.

Creating the Namespace

Before creating the namespace we need to understand why the namespace creation is required.

Namespaces provide uniqueness for each AppFabric user. On the Azure portal there will be multiple users or tenants using the services, in order to differentiate them the namespace is used. We need to create a namespace for using the AppFabric services.

The namespaces are multi-tenant which says that multiple users can share the same service. Tenants are isolated from each other using the namespace. The isolation is required for security and billing purposes.

So the namespace is actually tenant identifier. The Azure Portal advices to use the company name as namespace but the developer may do a call on it.

AppFabric Service

We can start with the steps in creating namespace.

Step 1 : Sign in to the Windows Azure Portal

After signing in, select the Service Bus, Access Control & Caching item.

AppFabric Service in windows azure

Step 2 : Click the New button

In the appearing view click on the New button from the ribbon as shown below.


Step 3 : Fill the details in Dialog

On clicking the new button the following dialog box appears. Enter the details of namespace in the dialog box.

AppFabric Bus Application

In the above dialog enter a namespace name and click the Check Availability button. The namespace should be unique across all the AppFabric users. (You need to select a different name other than the one shown above)

After finding a unique namespace select the other parameters.

Service Bus - Connection Pack Size

This parameter determines the number of connections and it requires real attention to understand it. If we select 0 connections, still we can create connection but charged at a higher rate. In real world situations we need to go for the other package which will prove to be cheaper.

The package options are shown below:

AppFabric Service cloud computing

For our testing purpose we can use the 0 connections option. Still we can create connections and this will be more cheaper than taking a 5 connections package.

Cache - Cache Size Quota

The Cache size allows us to specify the cache size pricing. The pricing will be based on the quota selected multiplied by month. The associated data transfers are also charged while using the AppFabric Caching service.

The Pricing information can be found here.

After entering the details click the Create Namespace button of the dialog box.

Step 4 : Wait for Activation

Wait for a few minutes and your namespace will be created and activated.

AppFabric Service

If the Status is Active, then you are ready with your namespace.


In this article we have discussed about AppFabric namespace, its uniqueness and demonstration of creating namespace. In the next article we can create a server for using the Service Bus feature.