Skip to main content

Patterns in Windows Azure Service Bus - Content-Based Router Pattern

In one of my latest post I talked about Resequencer Pattern, which can be used with success using Windows Azure Service Bus.  We saw how we can retrieve messages in the same order as they were sending to the Service Bus.
But what about Content-Based Router Pattern? The main scope of this pattern is the ability to route each message to different clients based on the data of each message. The system the process each message has to be able to redirect a message to a different consumer (client) based on the data that message contains.
One of the key features of this pattern is ability to change and maintained the rules that are used to redirect each message based on the content.
Windows Azure gives us the possibility to implement this pattern using Service Bus Topic. Each channel, where messages are redirected can be represented by a subscriber. As you already know each subscriber can have attached a filter that can filter messages based on the content. For this purpose we can use SqlFilter. Using SqlFilter we can look over the properties of a message and route them based on this purpose.
To be able to route messages based on the properties, we need to add the properties to our message. This step needs to be done on the producer side, on the system that produces messages, before adding them to the Service Bus Topic.
In the following example we will see how we can add these properties to our messages and how we can define these rules on the subscription side.
First step is to create the topic:
NamespaceManager namespaceManager = NamespaceManager.CreateFromConnectionString(
     CloudConfigurationManager.GetSetting(“ServiceBusConnectionString”));

if (!namespaceManager.TopicExists("myFooTopic"))
{
    namespaceManager.CreateTopic("myFooTopic");
}
After that, from the client side, we can create a message and send it to the topic. In our case we add a custom property named “property1”.
TopicClient topicClient = TopicClient.CreateFromConnectionString(
    CloudConfigurationManager.GetSetting("ServiceBusConnectionString"),
    "myFooTopic");

BrokeredMessage message = new BrokeredMessage();
message.Properties["property1"] = 10;
topicClient.Send(message);
>Next, we need to create the subscription that accepts only messages that have property equal to 10.
topicClient.AddSubscription("Property1Equal10", new SqlFilter( "property1 == 10") );
The last step is on the consumer side. We will consume message that are sent our subscription.
SubscriptionClient subscriptionClient = SubscriptionClient.CreateFromConnectionString(
    CloudConfigurationManager.GetSetting("ServiceBusConnectionString"),
    "myFooTopic",
    "Property1Equal10");

while(true)
{
   BrokeredMessage brokeredMessage = subscriptionClient.Receive();

   if (message != null)
   {
       try
       {
           ...
           message.Complete();
       }
       catch (Exception)
       {
           message.Abandon();
       }
      }
   }
}
There are a lot of cases when we can use this pattern. We can imagine a system that need to route messages based on the information contained in the message. For example we can have a system that process newsletters. Based on the content of the newsletters we want to redirect messages to the specific group of email. This can be very easily done using this pattern.
Last edit: A list of all patterns that can be used with Windows Azure Service Bus, that were described by me LINK.  

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP