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

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

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

Navigating Cloud Strategy after Azure Central US Region Outage

 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too