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 check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

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 …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…