Skip to main content

Windows Azure Service Bus - Schedule Message Delivery

Windows Azure Service Bus became a powerful mechanism to distribute messages in applications that are hosted in a cloud environment or in a system that has access to internet.
When we are using this service to notify different state change, I had moments when I need to signal a state change only after a specific time interval. To be able to support this functionality we need to be able to add the message to the topic only after the specific time elapsed. This means that we need to implement a component that can store this messages for a specific time interval. We will publish this message only after the specific time interval.
A new feature was added to Windows Azure Service Bus message. This new feature give us the possibility to make a message available in the topic only from a specific time. We can forget the component that we talked some lines ago. From now, this is supported by default. We have the support to specific the time from when the message will be available – in UTC format.
Before starting using this, we need to know a very important thing. This new feature guarantee that the message will be available only after the specific time, BUT we don’t have the guaranty that the message will be available from the next second. Based on the load of our Service Bus, this message can be made available on the specific time interval or after few seconds.
In the next example we will see how we create a message (BrokeredMessage) and specific the time when it will be available on the topic.
// Create the message
DateTime availableFromInUTC  = ... 
BrokeredMessage msg = new BrokeredMessage("some content");
msg.ScheduledEnqueueTimeUtc = availableFromUTC;

// Create message sender
MessagingFactory messageFactory = 
    MessagingFactory.CreateFromConnectionString(connectionString);
MessageSender messageSender = messageFactory.CreateMessageSender("topic1");

// Send the message to the topic
messageSender.Send(msg);
Another great feature on Windows Azure 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