Skip to main content

Service Bus Topics - Limitations

Until now we saw how we can use Service Bus Topics. Before starting to use it in a real project we need to know what are the current limitations that Service Bus Topics. In time, this limitation can change when a new version of Service Bus will be released. The following limitations are valid now, august 2012.
The size of a topic is set on creation. The maxim size accepted is 5GB. We can define a topic size from 1GB to 5GB. For Service Bus Topics we don’t need to pay the space used by the messages from the topic. Also when a message is received to a topic that exceeds the maxim size, a custom exception will be throw, which notify the client code about this problem. The good part is that we don’t have a limit of numbers that we have in a topic if we don’t exceed the maximum size of the topic.
For each topic we can have as many as 25 listeners. This is the maxim number of listeners on a relay. In the same time, the maximum numbers of relay listeners is limited to 2000. As we expect, an error is throw when this limit is reached (this behavior is for almost all limitation reached). As with the maxim number of listeners on a relay, we can have maximum 2000 subscribers per topic and a maximum 2000 SQL filter per topic. Don’t ask me from where this numbers appeared. One interesting thing here, each filter and action defined for a topic can have maximum 4KB size and each action can has as 64 expressions.
In the same order, a namespace can have as many as 10.000 topics and quest. Remarks, the maxim value is a sum between total number of Service Bus Queues and Service Bus Topics from a namespace.
The maximum size of a message is 254KB, from where the message header can have maximum 64KB. We can add as many properties we want to the header if we don’t exceed 64KB.
When we exceed one of these limitations an error is atomically throw in our code. Because of this is very easy to detect a kind or limitation reached.
In the next future I accept the limitation to disappear. Even now, I thing that for a normal application we can leave without any problem with this limitation and develop beautiful application over it.

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