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

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…