Skip to main content

Service Bus and Scalability

One of the beauty of cloud is scalability. You can scale as much you want, without having problem. Of course this is in theory. A cloud provider offer this feature to you, but a developer/architect needs to know how to use it in a way to design a high scalable system. Each cloud provider offer different points for scalability. We need to know very well what this points are and how we can use them in our benefit.
As a messaging system, Windows Azure offer us Windows Azure Service Bus. This a powerful service when an application needs a messaging system. But of course, Service Bus, as well as other services has its own limitations.
In this moment, the maximum number of subscription for a specific topic is 2.000. If we would have one client for each subscription that the maximum number of clients per topic is 2.000.
What should we do if we would have 10.000 clients?
It is clear that we cannot have 10.000 subscriptions per topic. We could send an email to Microsoft to ask them why they set this limit and if they could make an exception for us. But what we will do when we will hit 50.000 clients?
In this moment we need to identify exactly what is the scalability point. It is pretty clear the subscription number is not what we need. If we go one level up to the topics, than we will observe that this is a perfect scalability point for our application.
We can have an ‘unlimited’ number of topics over the same namespace or using multiple namespace. I thing that for all real scenario a namespace is sufficient. We should think to use more namespaces, if the load of the topics is pretty high, but this is not the subject for this blog post.
Based on the clients ID or name we can develop an algorithm that resolve the topic name for a specific client. For example if we have 10.000 clients we can have 10 topics. First 1000 clients will be redirected to topic ‘myTopic1’, from 1001 to 2000 will be redirect to ‘myTopic2’ and so on.

This could be a good solution, but we can have some problems using this approach. What is happening when the distribution of active clients will change? For example from 1 to 1000 interval, in 6 month we will have only 100 clients active. We can end up with hundreds of topics that are not used at their full potential. From the security perspective if we are using Shared Access Signature (SAS) we will need a service that will provide the access token for each client. Also, if we want to change the distribution algorithm over the topics and subscription we will need to deploy in the same time the new algorithm to all the backend services and clients devices – we know that this is not possible).
My approach would be to create a services that can provide to each client the full configuration that is used to access a subscription (namespace, topic, subscription and credentials). In this way it will be very easy to manage, update and track the subscription distribution over the system. All the subscription management will be done on the server side. When a client would have problem accessing his own subscription, he can interrogate the server and check the current configuration for it.

In this post we saw that Service Bus Topics and Subscription are very scalable, but the solution that we provide need to be also scalable. It is not enough to run our solution over a scalable infrastructure, we also need to design a scalable components.

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…