Skip to main content

Duplicate Detection in Windows Azure Service Bus

One great feature of Windows Azure Service Bus is the ability to identify the messages that are duplicate. Using this feature we can automatically remove messages from Service Bus Queue or Topic when we have more than one the same message. By default this mechanism is deactivated, but we can activate it very easily.
Let’s see how this mechanism works. When we activate this mechanism Windows Azure Service Bus will start to store a history with our messages. This period of time can be configures from only a few minutes to days. If a duplicate message is send to Service Bus, the service will automatically ignore the message.
Because the content of each message need to be serializable, the duplicate detection mechanism will look to the serialized items that were added to the message. If the content is the same, than the message will be consider as duplicate. For example we have the following class that we add to each message:
[DataContract]
public Foo
{
    [DataMember]
    public string Id { get; set;}
    [DataMember]
    public string Name { get; set;}
}
If we will add two messages with objects of type Foo with the same id and name, than the second message will be consider duplicate. We will not receive any kind of notification when we will try to send the second message.
MessagingFactory factory = MessagingFactory.Create([uri], [tokenProvider]);
MessageSender sender = factory.CreateMessageSender("FooQueue")

Foo obj1 = new Foo() { Id = “1”, Name = “One” };
BrokeredMessage message1 = new BrokeredMessage(obj1);

Foo obj2 = new Foo() { Id = “1”, Name = “One” };
BrokeredMessage message2 = new BrokeredMessage(obj2);

sender.Send(message1);
sender.Send(message2);
It is very important to remember that the duplicate detection mechanism will use the space from our Service Bus to persist the old messages. Because of this it is very important to be careful when we set the history time period.
This configuration can be made from two places. One is from portal, when we can activate this feature and set the history time period. This feature will be available only if you select “Custom create”.

The second place from where this can be configuration can done is from code. In the moment when we create a new Service Bus Topic or Service Bus Queue we can specify in the create command. To be able to do this we will need to create a TopicDescription or a QueueDescription object. In this object we can activate this functionality and set the history time period.
Topic:
TopicDescription fooTopicDescription = new TopicDescription("FooTopic")
    {
        RequiresDuplicateDetection = true,
        DuplicateDetectionHistoryTimeWindow = new TimeSpan(10, 0, 0),
    };
namespaceManager.CreateTopic(fooTopicDescription);
Queue:
QueueDescription fooQueueDescription = new QueueDescription("FooQueue")
    {
        RequiresDuplicateDetection = true,
        DuplicateDetectionHistoryTimeWindow = new TimeSpan(10, 0, 0),
    };

namespaceManager.CreateQueue(fooQueueDescription);
These policy settings of Service Bus Queue or Service Bus Topic can be changed only on creating time. After this, if we want to change the history time period or to deactivate it, it will not be possible. To be able to do this, you will need to delete the resource and recreate it.
This is a great feature that can be used when we need to avoid duplicate messages to be added to our Service Bus.

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…