Service Bus Brokered Message API Details

Posted: March 16, 2013 in WCF, Windows Azure

In this blog I will focus mainly on the .Net platform, you can find all the related classes for the Service Bus Brokered Messaging in the following namespaces: Microsoft.ServiceBus and Microsoft.ServiceBus.Messaging

As you may know that based on my previous blog post about the Windows Azure Service Bus Brokered Messaging that mainly works using queues or topics and subscriptions. To work with the Service Bus Brokered Messaging you have to be well familiar with the Microsoft.ServiceBus.Messaging namespace because all the related functions is in this namespace, for the Relayed Messaging, most of its classes and functions will be in Microsoft.ServiceBus namespace.

Let me introduce you the main classes that you will certainly have to use during the development:

  • BrokeredMessage:

    it is the unit that communicate the service bus clients together. Like the storage you will have to identify the type of your client whether it was the queue, topic or a subscription client.

  • NamespaceManager:

    The NamespaceManager is what is responsible for runtime of the operations of the service bus messaging entities from inserting, creating, deleting and so on.

  • MessagingFactory

    The lifecycle of the messaging is tracked, monitored and totally handled by the Messaging Factory.

Now let’s start understanding the Brokered Message API using the Queue. You can find a small demo about it in the following link. If you are using the queue here are the main classes related:

  • QueueClient: that’s what represents the object responsible for the communication between the service bus
  • QueueDescription: this is what represents the metadata related

Talking about the next type of Windows Azure Service Bus Brokered Relay, the Topic & Subscription. They will always consume the same classes as the Queue like the BrokeredMessage, the NamespaceManager and the MessagingFactory. Adding to those, the specified clients:

  • TopicClient

    This is the object responsible of sending the data to the service bus client subscriber to the specified topic.

  • TopicDescription

Metadata about the service bus topic.

  • SubscriptionClient

    This is the object responsible of receiving the brokered message from the service bus depending in the subscribed topic.

  • SubscriptionDescription

    Metadata about a specified service bus subscription.

For better understanding all about the Microsoft.ServiceBus .Net class, I would recommend you download the following document. For the Brokered Messaging class, I would recommend you go through the Microsoft.ServiceBus.Messaging document which will certainly help you getting along the development with Service Bus Brokered Message. It contains all the details required about the Windows Azure Service Bus Namespaces with all its classes and its functions too.

For more general information about the Service Bus here is the link of my source.

For more information about Service Bus API using .Net kindly find it on the following link.

For more information about Service Bus API using Node JS kindly find it on the following link.

For more information about Service Bus API using Python Kindly find it on the following link.

For more information about Service Bus API using Java kindly find it on the following link.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s