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

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(...

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

Navigating Cloud Strategy after Azure Central US Region Outage

 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provi...