未加星标

Bend Message Deduplication on Azure Service Bus to Your Will

字体大小 | |
[系统(windows) 所属分类 系统(windows) | 发布者 店小二05 | 时间 2016 | 作者 红领巾 ] 0人收藏点击收藏

Bend Message Deduplication on Azure Service Bus to Your Will

Duplicates detection functionality provided by Azure Service Bus can automatically remove duplicate messages sent to a queue or topic. Deduplication is always based on the value of the MessageId property. No other property can participate in deduplication.

In the real world, message deduplication can often depend on things that are part of the message payload itself. Let's say we process orders. Deduplication would rather be based on the order ID and not message ID. There are a few creative solutions that allow custom deduplication. For example, perform deduplication outside of ASB broker by manually inspecting message payload and marking it as a duplicate. For example, using Azure Functions and Storage tables*. While approach like this one works, it has several drawbacks:

Unnecessary intermediate steps Performance decrease No ability to take advantage of highly optimized and performant native deduplication

What's the solution?

Use native deduplication!

Wait, but isn't native deduplication limited to solely message ID?

Glad you've asked. Absolutely. It is. Though let's look at the MessageId property of the BrokeredMessage . It's a read/write property, meaning we can set it to custom values.

Custom value you said?

Let's read a bit more of the ASB documentation on deduplication.

To enable duplicate detection, each message has to have a unique MessageId property that by default stays the same no matter how many times the message is read from a queue.

Solved! To deduplicate order messages on OrderId , we'll assign brokered message MessageId property the value of OrderId . Done. Now order messages will be deduplicated on order IDs**.

Hold your horses! What if I need to deduplicate based on several values from a message?

Same as with order id. Combining all property values and assigning as MessageId . Except that there might be a size issue.

Size issue?! Yes. BrokeredMessage.MessageId is limited to 128 characters. Would that be a deal breaker if generated ID needs to be more than 128 characters? Not at all. As a matter of fact, the entire payload could be used for deduplication. Here's an example:

var payload = serializerOfYourChoice.Serialize(payloadObject); var msg1 = new BrokeredMessage(payload); msg1.MessageId = CreateDeterministicIdFromHash(payload); msg1.Label = "1st"; await sender.SendAsync(msg1).ConfigureAwait(false); var msg2 = new BrokeredMessage(payload); msg2.MessageId = CreateDeterministicIdFromHash(payload); msg2.Label = "2nd"; await sender.SendAsync(msg2).ConfigureAwait(false);

The sample creates a GUID like ID by making an object hash using serialized object. For example, using JSON.Net you could get the serialized object and pass it to CreateGuidLikeIdFromHash to provide the deterministic ID that is based on a hash. The method could be implemented in the following way:

static string CreateDeterministicIdFromHash(string input) { var inputBytes = Encoding.Default.GetBytes(input); // use MD5 hash to get a 16-byte hash of the string using (var provider = new MD5CryptoServiceProvider()) { var hashBytes = provider.ComputeHash(inputBytes); return new Guid(hashBytes).ToString(); } }

Et voilà. Now you can leverage native ASB deduplication using your custom data from the message itself without unnecessary intermediaries or performance impact.

Stay deduplicated!

* deduplication with Azure Functions sample by Michael Stephenson

** RequiresDuplicateDetection needs to be set to true along with DuplicateDetectionHistoryTimeWindow set to the time span duplicates detection is taking place per message

本文系统(windows)相关术语:三级网络技术 计算机三级网络技术 网络技术基础 计算机网络技术

主题: .NetASB
分页:12
转载请注明
本文标题:Bend Message Deduplication on Azure Service Bus to Your Will
本站链接:http://www.codesec.net/view/507485.html
分享请点击:


1.凡CodeSecTeam转载的文章,均出自其它媒体或其他官网介绍,目的在于传递更多的信息,并不代表本站赞同其观点和其真实性负责;
2.转载的文章仅代表原创作者观点,与本站无关。其原创性以及文中陈述文字和内容未经本站证实,本站对该文以及其中全部或者部分内容、文字的真实性、完整性、及时性,不作出任何保证或承若;
3.如本站转载稿涉及版权等问题,请作者及时联系本站,我们会及时处理。
登录后可拥有收藏文章、关注作者等权限...
技术大类 技术大类 | 系统(windows) | 评论(0) | 阅读(36)