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

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