Skip to main content

A hot fix for a Service Bus problem

In this post we will talk about a performance problem that occurred in an application that is using Service Bus On-premises. But the problem and solution is applicable also for any other system that is using not only Service Bus On-premises but also Azure Service Bus.

Context
We have an application that process a specific type of messages that are coming through Service Bus. Our application has a dedicated Topic that is used only by them. A Subscription from another Topic forward automatically the messages to our application topic.
The current requirement requires that we need to write in logs all the messages that we are reading from our Application Subscription, even the one that we don’t need to process. The system that push messages to our Topic, is pushing a lot of messages to our topic, even messages that we don’t need to process, but because we need to log all messages that we receive we add a filter to our Subscription to receive and consume only the messages that we care.
The application cannot scale by adding more instances. Only one instance of our app can run, we can only scale up by adding more horse power (CPU, Memory).

Problem
Because of this we can end up with millions of messages, where only 2-3% of them are messages that need to be process. A Topic can reach a limited size and because of the noise that the other system sends to us we end up with millions of messages that stays in the queue.
The application was design in such a way that cannot scale. When the load is medium, we reach easily 3-4M messages in the subscription (it seems that when we reach 4M messages, we start to have stability problem).


What we can do consume all this messages, but reducing the load on our application with minimal costs?
Of course we could say that we should change the system that push messages to not push messages that we don’t need, but this is not possible. Another solution is to add a filter on our subscription to ignore messages that we don’t care, but this is not possible also because we need to log all messages that were send to our Subscription (Topic).

Solution
A simple solution that I see, that would be compliant will the given context is to create on our topic one more subscription. On our initial subscription we would add a filter that would accept only the messages that we need to process, and a second subscription that accepts messages that we don’t care, but we need to log.
We can listen to our the second subscription with another application or with even a listener that is running in the same process like our main application and the only thing that he does is to log the message in our logger.




In this way, even if we cannot scale our application, by adding more resources, we can eliminate from our Topic as soon as possible the messages that we don’t care (having control on the size of the Topic/Subscription) - having control on the Topic size.

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 …

[Post-Event] Codecamp Conference Cluj-Napoca - Nov 19, 2016

Last day I was invited to another Codecamp Conference, that took place in Cluj-Napoca. Like other Codecamp Conferences, the event was very big, with more than 1.000 participants and 70 sessions. There were 10 tracks in parallel, so it was pretty hard to decide at  what session you want to join.
It was great to join this conference and I hope that you discovered something new during the conference.
At this event I talked about Azure IoT Hub and how we can use it to connect devices from the field. I had a lot of demos using Raspberry PI 3 and Simplelink SensorTag. Most of the samples were written in C++ and Node.JS and people were impressed that even if we are using Microsoft technologies, we are not limited to C# and .NET. World and Microsoft are changing so fast. Just looking and Azure IoT Hub and new features that were launched and I'm pressed (Jobs, Methods, Device Twin).
On backend my demos covered Stream Analytics, Event Hub, Azure Object Storage and DocumentDB.

Title:
What abo…