Skip to main content

Patterns in Windows Azure Service Bus - Dynamic Router Pattern

Last time we talked about Scatter-Gather Pattern and how we can implement it using Windows Azure Service Bus. Today, we will look over Dynamic Router Pattern and how can be integrated in Windows Azure Service Bus.
First of all, let’s see what Dynamic Router is. This is a pattern that can be used when we want to register at runtime different rules and based on this rules the messages are redirected to a specific consumers. This sounds pretty simple in the first moment, but we have 2 different situations that need to be handled.
The first one is from the consumer perspective.  In any moment we need to be able to change the rules or add new rules, without stopping the system. These rules can use properties from messages that didn’t exist when the system started.
The second situations are from the producer. At runtime we need to be able to add or remove properties that can be handled by the system when the routing is made without restarting the system or affecting the consumers.
Top on this, it would be nice to be able to extract all the properties that will be used by the routing mechanism automatically, without the need to make special configuration over the system.
Of course, this pattern can be implemented with success using Windows Azure Service Bus. This pattern can be implemented using Service Bus Queues or Service Bus Topics. The secret here to have the best implementation of this pattern in Windows Azure is to create a mechanism that can extract the properties that are needed by the dynamic routing from the message that is added to the Service Bus. This solution need to be very flexible and to give us the possibility at runtime to control this.
The solution of this problem can be the promoted properties that can be found in BizTalk. This kind of properties doesn’t exist yet in Windows Azure Service Bus, but can be implemented very easily using attributes. I describe this solution in the following blog post: http://vunvulearadu.blogspot.ro/2012/10/winduws-azure-service-bus-adding.htm
In this moment we know how we can dynamically add/remove properties from a BrokeredMessage. From now one, the rest can be implemented very easily. If we are using Windows Azure Service Bus Topic, we can create custom filters over each subscription.
TopicClient topicClient = TopicClient.CreateFromConnectionString(
CloudConfigurationManager.GetSetting(
    "ServiceBusConnectionString"),
    "myFooTopic");
SqlFilter sqlFilterReviewGroup = new SqlFilter(“Groups LIKE ‘%Review%’”);
topicClient.AddSubscription(“ReviewSubscription”, sqlFilterReviewGroup);
SqlFilter sqlFilterTestGroup = new SqlFilter(“Groups LIKE ‘%Test%’”);
topicClient.AddSubscription(“ReviewSubscription”, sqlFilterTestGroup);
This pattern can be used with success when we need a dynamic routing mechanism where rules and filters attributes can change anytime. This is a case that can appear when we offer a solution that is used by other solution providers.
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…