Skip to main content

Service Bus Queues from Windows Azure - BrokeredMessage content

In this blog post I'll continue the blog posts series about Service Bus Queue. In this post we will talk about what and how we should add information’s to a BrokeredMessage. Theoretically, this applies also to Service Bus Topics because in both cases we use BrokeredMessage.
We will start with a simple example. We have the following class with information that we want to add to the queue.
public class Foo
{
public string Name { get; set; }
public decimal Value { get; set; }
public int CustomerId { get; set; }
}
In this case we have two options. We can make this object serializable and specify the object in the constructor. This is a solution for our problem, but do we really need to add attributes and add the entire object to the queue.
Another solution for our problem is to add all this information to the properties collection of BrokeredMessage. We have collection properties in the BrokeredMessage that we can set that are based on an IDictionary . Theoretically we can add our Foo instance as a property or we can add each field that we want to put in the message as a separate property.
BrokeredMessage message = new BrokeredMessage();
message.Properties["Name"] = foo.Name;
message.Properties["Value"] = foo.Value;
message.Properties["CustomerId"] = foo.CustomerId;
or
message.Properties["currentInstance"] = foo;
Any object that is added to a BrokeredMessage need to be serializable. What solution should be used... hmm depends.
If we have already an object that is used to store all the content that need to be added to the BrokeredMessage that we can put the whole object to the BrokeredMessage. If we don't have this kind of object or our object contains data that should not be added to the BrokeredMessage that we should add separately each property or create an object for this purpose.
What about if we have a lot of information that we need to add to the message. First of all do we need all this information? Can we store this information in another place? For example if we have a picture we could store it on the blob or in another kind of repository. If we don't have any other option we can split the content in more messages and use SessionId. I explained how we can do this in this post: http://vunvulearadu.blogspot.hu/2012/08/service-bus-queues-from-windows-azure_20.html
If we need to add a stream to a BrokeredMessage the first thing that I would say is: "Do you really need this?” It is possible, but I would try to think twice before adding stream content to it.
To set the content of a message from the stream we need to specify in constructor our stream. The consumer will need to call the GetBody() method to get the current stream from the message.
--- Producer ---
byte[] currentMessageContent = new byte[100];
...
BrokeredMessage currentMessage = new BrokeredMessage(
new MemoryStream(currentMessageContent),
qc.Send(currentMessage);
--- Consumer ---
Stream messageStream = message.GetBody<Stream>();
BrokeredMessage implement IXmlSerializable interface. So bassicaly on the queue, this will an XML content. Also we can set a label to each message:
message.Label = "SomeLabelText";
If you design your application to process a message and after that to forward another BrokeredMessage to another queue a message has the property "ReplyTo". This string property can be used when we want the queue that can be used to reply to a given message - we could create a chat very easily, where each user whould have is own queue :-)
BrokeredMessage implement the IDispose interface with a scope. Please don't forget to call it. Because we can do operations on Service Bus Queues asyncron, we need to be carefully when we call the Dispose method. Only on the callback of the Complete method or DeadLetter we could call it.
In this post we saw how we should add data to a BrokeredMessage. We can use not only the body of the message but also the property collection. Any kind of data that is serializeble can be added to a BrokeredMessage.

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(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP