Skip to main content

Patterns in Windows Azure Service Bus - Resequencer Pattern

Today we will talk about another message pattern: Resequencer. In the last post I presented Recipient List Pattern. In comparison with this pattern, Resequencer Pattern is very different. The main scope of this pattern is to help us to put messages back in a specific order.
When we are talking about messages, we can talk about a stream of messages that need to be received in a specific order. It is very crucial for the receiver to retrieve the messages in the same order he receives.
Theoretically, in a simple case we will receive messages in the expected order. This is offer Service Bus by default. But what happen if an error occurs on the receiver and message is putted back in the queue. We will need to retry to consume that message one more time and not the next message.
Another case when the order can be broken is when we have more than one producer. For this case we can have two different situations.
In the first scenario, each producer will produce messages for different stream of messages. In this case we can very easily use the session id of the messages to be able to receive only messages for a specific stream. But we will still need a way to detect if the messages if the message that we expect. First step is to add two properties to each message. The first property will tell us how many messages are in this message stream and the other one will tell us the index of the current message. Base on this information, the receiver will know the index of the next message and will be able to validate it. If we will receive messages that don’t have a valid index id, we can throw them in the defer queue, from where we will be able to retrieve them anytime.
QueueClient  queueClient = …
BrokekedMessage message = new BrokeredMessage();
message.Properties[“index”] = 1;
message.Properties[“count”] = 10;
message.SessionId = 123;
MessageSession messageSession = queueClient.AcceptMessageSession(123);
int currentIndex = 1;
    BrokeredMessage message = messageSession.Receive();
    if(int.Parse(message.Properties[“index”]) != currentIndex)
    if(int.Parse(messsage[“count”]) == currentIndex)
Next we need to take message that were marked as dead letters and moved automatically to the dead letter queue.
QueueClient deadLetterQueue = QueueClient.CreateConnectionString(
while (true)
    BrokeredMessage message = deadLetterQueue.Receive();
    // same logic as in the normal queue.
    // we need to abandon the message and not to mark him as dead letter.
    // we already process the dead letter messages
The second scenario is a little more complicated. In the same queue, we have more than one producer that produce message for a specific stream. The chances to have messages in the expected order are very low. The solution is similar to the first one. We can add the index of each message and total number of messages as properties to the message that is added to the queue. The consumer can check this values and when the message index is wrong, the message will be added to the defer queue.
In the both solutions, the most time consuming is retrieving the message from the defer queue. The good part that usually the messages are in a kind of order, even if is not perfect (eq. 1 3 5 2 6 7 10 8 9). Because of this we will not need to “iterate” through the defer queue to many times.
This pattern can be used for cases when it is critical to process messages in a specific order. In a system that sells tickets for a baseball game this is not so critical. But for a system that receives commands using messages it is very important to execute the commands in the same order – for example a nuclear power station.
This is a pattern that is not very common. When you reach a case where you need this pattern, try to double check again if you need it, because this pattern can be very expensive – from the perspective of processing time and resources.
Last edit: A list of all patterns that can be used with Windows Azure Service Bus, that were described by me LINK.  


Popular posts from this blog

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 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 …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.