Skip to main content

Patterns in Windows Azure Service Bus - Message Filter Pattern



In the last post I tacked about Splitter Pattern.Today we will continue with Message Filter Pattern. This pattern can be used with success with Windows Azure Service Bus.
As the name says, all the messages are filtered based on specific rules. Any message that will reach the consumer will be filter based on this rules. All the producers will use the same entry point where they will add messages. They don’t have to know that messages are filtered based on same rules. In this way, the message system will create a decoupling between the producer and the consumer. This pattern is used to be able to control the messages that where not routed to any subscriber.
Windows Azure Service Bus Topics can be used for this purpose. It gives us the ability to define rules that can check the messages content based on meta-information. These rules will be added to each subscriber and will specify if the messages will be accepted or not.
SqlFilter myCustomFilter =
    new SqlFilter("grade < 5");
namespaceManager.CreateSubscription(
               "StudentsGradesTopic",
               "StudentsWithProblemsSubscription",      
               myCustomFilter);  
 In the following example I created a subscription that accept messages that have the grade under 5. For more information about defining custom rules: http://www.vunvulearadu.blogspot.hu/2012/08/service-bus-topics-how-to-use-it-part-2.html
When we are using this pattern, consumers will only receive and process messages that where filtered. Because of this, we can have messages in the system that will not pass any filter. This messages need to be tracked in one way or another. For these situations we can define a custom rule in Service Bus Topic that will receive messages that didn’t pass the rest of the rules of the subscribers. The name of the filter expression is “MatchNoneFilterExpression”. In the following example we setup a rule that accept messages that didn’t pass the rest of the rules.
RuleDescription notConsumedMessagesRule = new RuleDescription()
{
     FilterAction = new SqlFilterAction(“set isNotConsumed = true;”),
     FilterExpression = new MatchNoneFilterExpression()
};
subscription.Add(notConsumedMessagesRule);

This pattern can be used with success when we need to control what kind of messages is received by each consumer. We can imagine that we need to manage grades from a university. For this purpose each department want to receive information related to them. The history department doesn’t want to receive grades from the mathematic department. For this case the Message Filter Pattern can help us a lot because it created only one entry point for the applications and services that add these messages.
Last edit: A list of all patterns that can be used with Windows Azure Service Bus, that were described by me LINK.  

Comments

  1. With Library 1.7 I don't see MatchNoneFilterExpression class in any of the dll.
    How do I implement this pattern without MatchNoneFilterExpression?

    ~Bhavya

    ReplyDelete
    Replies
    1. Look here: http://vunvulearadu.blogspot.ro/2012/12/windows-azure-service-bus-topic-detect.html

      Delete
    2. thanks Radu. Will give it a try and let you know.

      Delete

Post a Comment

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…