Skip to main content

Updating content of messages from Azure Queues

In the era of microservices and cloud, applications contain more and more components and sub-components that are design to do only one thing. All this components needs to communicate between each other in a fast and reliable way.
For communication purpose, different messaging solutions are used. Nowadays, a Enterprise Service Bus solution like Azure Services Bus Topic or BizTalk is normal. For more simple problems, one or more queues can be enough (Azure Storage Queue)

Almost all messaging system allow us to consume messages using Peek and Lock pattern. This allow us to take a message from the queue, lock it for a specific time, process it and at the end, if we are able to process it with success to remove it from the queue. During this time, the message is hidden from others consumers and cannot be peeked by others. After a specific time interval if we don't mark the message as consumed the message will be available in the queue for consuming.

But what should we do when we have a long running processing task, that can take 20 minutes or 1 hour. The most simple solution would be to split the task in subtasks - when is possible.
This means that we would have multiple sub-components that needs to communicate between each other. We would end up with multiple queues or with an enterprise service bus system like Azure Service Bus Topic.

But what should we do when we cannot split it? Or the complexity of splitting in subtasks is so high that it not worth it... and even if we would be able to split it in subtasks, we would end up with something similar like a 'state machine'. This state would be used to know the current status of the tasks and would allow us to be able to continue from the last step. For this case, it would be nice to be able to update the content of a message that is the queue without having to remove the original message.

For long running tasks this could be very useful. We could update the current progress/status of task in the queue, without having to use a storage for this. This can be done very simple if we are using Azure Storage Queue. This queue system allow us to update an existing message that is the queue. See below code:
CloudQueue queue = queueClient. GetQueueReference("fooqueue");

CloudQueueMessage message = queue.GetMessage(new TimeSpan(0,0,10);
String newMessageContent = message + " new message content";

queue.UpdateMessage(message, MessageUpdateField.Content);
We can use this feature each time when we need to update the progress of a task that was triggered by a message in the queue. Beside the content we can update any other fields of the message (for example the visibility property).

In this post we saw how simple is to update the content of a message from a queue without having to remove and recreate it.


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

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

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…