Skip to main content

Service Bus Queues from Windows Azure - Scheduling

Today I will continue discussion about Service Bus Queue with X topics.
Let’s assume that we have messages that we need to deliver on the queue only on a specific type. How should we do this? First solution that can come in our mind is to create a service, something like a schedule that will add the message to the queue only on a given time. This is a possible solution, but we need to develop a service, we need to host this. All of this means money and resources.
Another simple solution is to use the scheduled functionality that is offered by the Service Bus from Windows Azure. Any message that is added to the Service Bus Queue can be scheduled. Each message that is created can have the property “ScheduledEnqueueTimeUtc” set to a given value. When this value is not set the message is automatically added and available to the queue. When we set this value, the message will enqueued to the queue only at the specific time.
From the code, the only thing that we need to do is to set this property. Is not need to specify something when we send this message or something similar.
QueueClient qc =
QueueClient.CreateFromConnectionString(
myFooConnectionString, "FooQueue");
BrokeredMessage message = new BrokeredMessage();
message.Properties["Name"] = "Radu Vunvulea";
// The message will be enqueue in 1 hour from the current time.
message.ScheduledEnqueueTimeUtc = DateTime.UtcNow.Add( new TimeSpan(0,1,0,0));
qc.Send(message);
As you can see is quite simple to do something like this. We don’t have to reinvent the wheel. This functionality is already built in in Service Bus. Next we will talk how we can integrate WCF to Service Bus.

Comments

Popular posts from this blog

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Can User Technical Profile Influence AI Architecture Decisions?

In the last few days, I ran a small experiment on Devin/Windsurf/Cascade, BMAD, and LLM-based architecture decisions. The initial concern was simple: if an AI coding assistant knows something about the user, for example, that the user is a Java developer or a .NET developer, can this information influence the architecture and technology stack that the AI will propose? This question is important because many companies are starting to use AI tools not only for coding but also for product discovery, architecture, documentation, and technical decision-making. If the AI is influenced by the developer's personal profile, the result may not be fully neutral. It may look like a business or architecture decision, but in reality, it may be partially shaped by the context of the person using the tool. The test was done using BMAD with Devin/Windsurf/Cascade. The scenario was a unified field service operations platform. The task was to let BMAD refine the product, define the architecture and s...

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.51 EF 6.0.2 VS2013 It see...