Skip to main content

Service Bus Topic - Different ways to create and manage it

In the last post, we saw how easily we can integrate Service Bus Topic with WCF. Today topic is simple. There are times when we need to create topics and subscriptions that are valid for one day or two. Not only this, this task can sometimes be done by various persons of applications. Let’s see what our options are.
Of course the most powerful tool is the code. From code we can create topics, subscriptions and configure them in any way we want. When we create a topic we can set the default TTL value of messages that will be send to the topic, but we will not be able to set a property that specify the TTL of the topic (delete after 2 days for example). But, beside this we can set others values like the maximum size of the topic, enable or disable the batch operations and if the message duplication detection is activated. Similar configurations can be made to a subscription using SubscriptionDescription.
TopicDescription topicDescription = new TopicDescription()
{
RequiresDuplicateDetection = true;
}
In this moment we cannot specify from configuration file (or any kind of XML) a new topic or a new subscription or to reconfigure one of them. If we need something like this we can very easily create a small application for this purpose.
The last way to create topics and subscriptions is from Windows Azure portal. This can be created from the portal using only the mouse. All the main properties can be configures from here. We need to go the Service Bus tab. In this tab we will have buttons than give us the ability to create topics and subscriptions. The only limitation is on subscriptions, we cannot create filters and actions for them. Because of this a subscription created from the portal will receive all the messages.

Another way to create them (that I don’t enjoy) is by HTTP requests. Yes, using simple HTTP request we can create and manage Service Bus. The assembly that we use from the code to create a topic is only a wrapper over HTTP requests. Because the topic is quite complex, please find more information about this in the following link: http://msdn.microsoft.com/en-us/library/windowsazure/hh780752.aspx
We saw that we can create and manager topics in various ways. Because all the commands can be executed over HTTP/HTTPS we can create any configuration tool (and also use Service Bus) from any language and platform. This can be great when we want to integrate it in a big and old system that is written in Perl or from COBOL (that use a library like Libcurl).

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