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

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills)

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills) The idea that moving to the cloud reduces the costs is a common misconception. The cloud infrastructure provides flexibility, scalability, and better CAPEX, but it does not guarantee lower costs without proper optimisation and management of the cloud services and infrastructure. Idle and unused resources, overprovisioning, oversize databases, and unnecessary data transfer can increase running costs. The regional pricing mode, multi-cloud complexity, and cost variety add extra complexity to the cost function. Cloud adoption without a cost governance strategy can result in unexpected expenses. Improper usage, combined with a pay-as-you-go model, can result in a nightmare for business stakeholders who cannot track and manage the monthly costs. Cloud-native services such as AI services, managed databases, and analytics platforms are powerful, provide out-of-the-shelve capabilities, and increase business agility and innovation. H...

Cloud Myths: Migrating to the cloud is quick and easy (Pill 2 of 5 / Cloud Pills)

The idea that migration to the cloud is simple, straightforward and rapid is a wrong assumption. It’s a common misconception of business stakeholders that generates delays, budget overruns and technical dept. A migration requires laborious planning, technical expertise and a rigorous process.  Migrations, especially cloud migrations, are not one-size-fits-all journeys. One of the most critical steps is under evaluation, under budget and under consideration. The evaluation phase, where existing infrastructure, applications, database, network and the end-to-end estate are evaluated and mapped to a cloud strategy, is crucial to ensure the success of cloud migration. Additional factors such as security, compliance, and system dependencies increase the complexity of cloud migration.  A misconception regarding lift-and-shits is that they are fast and cheap. Moving applications to the cloud without changes does not provide the capability to optimise costs and performance, leading to ...