Skip to main content

Service Bus Topics - Define custom rules for messages that don’t respect any rule defined in a topic

In one of my older post I tacked about how we can define filters for each subscriber of a Service Bus Topics. We saw how we can filter messages for a subscriber based on some rules that are defined using FilterExpression:
RuleDescription ruleDescription = new RuleDescription()

{

    Action = new SqlRuleAction("set isValid= false"),

    Filter = new SqlFilter("value = 10");

}

namespaceManager.CreateSubscription(

    "myFooTopic",

    "seccondSubscription",

    ruleDescription);

var subscription = namespaceManager.CreateSubscription(

    "myFooTopic",

    " thirdSubscription");

subscription.Add(ruleDescription);

Using these rules is quite simple to define custom rules for the messages from a topic. But what about messages that don’t respect any rules defined in our topic? How we can detect these messages and define a custom rule for them. In a perfect word we can control the messages that arrive in our topic, but in a distributed system these thing doesn’t happen all the time.
For this cased we can use “MatchNoneFilterExpression” that will route to our topic all the messages that were not consumed by our subscribers. For example in our example we only consume messages that have the value equal with 10. What about the rest of the messages? Of course we can define a rule for values that are not equal with 10, but if we have more subscribes with different rules it will complicated to define the non-true rules for all the subscribers.
 RuleDescription notConsumedMessagesRule = new RuleDescription()

 {

     FilterAction = new SqlFilterAction(“set isNotConsumed = true;”),

     FilterExpression = new MatchNoneFilterExpression()

 };

 subscription.Add(notConsumedMessagesRule);
In the above example our rule adds a property named “isNotConsumed” and set the value to true. Based on this rule we will able to route this messages to a specific subscriber.
In the same way we have another filter expression that is used when we want to define a rule for the messages that match all the filter expression from all our rules – MatchAllFilterExpression.
RuleDescription matchAllRule = new RuleDescription()
 {
     FilterAction = new SqlFilterAction(“set matchAll = true;”),
     FilterExpression = new MatchAllFilterExpression()
 };
 subscription.Add(matchAllRule);

Using this filter expression we can define custom rules for messages that didn’t respect any defined rule or messages that respect all the rules from our topic. In the end I want to enumerate the filter expression that can be used in this moment:
  • CorrelationFilterExpression
  • MatchNoneFilterExpression
  • MatchAllFilterExpression
  • SqlFilterExpression

Comments

Popular posts from this blog

Why Database Modernization Matters for AI

  When companies transition to the cloud, they typically begin with applications and virtual machines, which is often the easier part of the process. The actual complexity arises later when databases are moved. To save time and effort, cloud adoption is more of a cloud migration in an IaaS manner, fulfilling current, but not future needs. Even organisations that are already in the cloud find that their databases, although “migrated,” are not genuinely modernised. This disparity becomes particularly evident when they begin to explore AI technologies. Understanding Modernisation Beyond Migration Database modernisation is distinct from merely relocating an outdated database to Azure. It's about making your data layer ready for future needs, like automation, real-time analytics, and AI capabilities. AI needs high throughput, which can be achieved using native DB cloud capabilities. When your database runs in a traditional setup (even hosted in the cloud), in that case, you will enc...

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

[Post Event] Azure AI Connect, March 2025

On March 13th, I had the opportunity to speak at Azure AI Connect about modern AI architectures.  My session focused on the importance of modernizing cloud systems to efficiently handle the increasing payload generated by AI.