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 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...

Can User Technical Profile Influence AI Architecture Decisions?

In the last few days, I ran a small experiment on Devin/Windsurf/Cascade, BMAD, and LLM-based architecture decisions. The initial concern was simple: if an AI coding assistant knows something about the user, for example, that the user is a Java developer or a .NET developer, can this information influence the architecture and technology stack that the AI will propose? This question is important because many companies are starting to use AI tools not only for coding but also for product discovery, architecture, documentation, and technical decision-making. If the AI is influenced by the developer's personal profile, the result may not be fully neutral. It may look like a business or architecture decision, but in reality, it may be partially shaped by the context of the person using the tool. The test was done using BMAD with Devin/Windsurf/Cascade. The scenario was a unified field service operations platform. The task was to let BMAD refine the product, define the architecture and s...

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.51 EF 6.0.2 VS2013 It see...