BrokeredMessage message = new BrokeredMessage();
message.Properties.Add(“Groups”,”Review, Test”);
…
Each subscriber will need to create a custom filter. For this purpose we can use the ‘LIKE’ operator of SqlFilter. TopicClient topicClient = TopicClient.CreateFromConnectionString(
CloudConfigurationManager.GetSetting(
"ServiceBusConnectionString"),
"myFooTopic");
SqlFilter sqlFilterReviewGroup = new SqlFilter(“Groups LIKE ‘%Review%’”);
topicClient.AddSubscription(“ReviewSubscription”, sqlFilterReviewGroup);
SqlFilter sqlFilterTestGroup = new SqlFilter(“Groups LIKE ‘%Test%’”);
topicClient.AddSubscription(“ReviewSubscription”, sqlFilterTestGroup);
Even if this solution will work without any kind of problem, we should be aware that we use the “LIKE” operator. From performance perspective we know that this is not the fastest solution. If we don’t have a lot of messages that are send on the wire that this is not a reals issue. For better performance we can find different solutions, from complicated one that use bits to simpler one like adding different property for each group. In this way the subscriber of a filter will only need to check if the property is set or not. For this purpose we can use the “EXISTS” operator or SqlFilter. SqlFilter sqlFilterReviewGroup = new SqlFilter(“EXISTS Review”);
topicClient.AddSubscription(“ReviewSubscription”, sqlFilterReviewGroup);
If you don’t want to have a lot of properties you can a prime numbers. The only problem with this solution is related to how easy the code can be read and maintain. Each prime number can represent a different group. And a message should be received by a subscription if the group property can be divided to the prime number that represents our group. We could imagine another solutions also.To be able to use this pattern we need to define the list of recipients. This list can be a static list of can be created dynamically and can be change on runtime. Using Service Bus Topics from Windows Azure the list can be dynamically created and changing the list will not require changing the code that send or receive the messages. All this can be done in the configuration files.
The important thing that we need to remember about Recipient List Pattern is when we need to use it and Windows Azure Service Bus supports an implementation of this pattern.
Last edit: A list of all patterns that can be used with Windows Azure Service Bus, that were described by me LINK.
0 comments:
Post a Comment