You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I see libraries like Rebus and MassTransit implement their own version of the Claim Check pattern. However, all of these typically involve modifying the DTO structure to support claim check, which in my view defeats the purpose. I believe claim check should be transient -- if a serialized payload size is greater than some configurable threshold, then instead of being sent as the message body, it should be stored in some configurable data store (e.g. S3, DynamoDB) and a claim check ID header should be added to the message.
On the receiving end, if the claim check header exists, pull data from that storage layer and deserialize it into the final strongly-typed DTO structure the consumer wants.
Because I do not see any available implementations that do claim check transparently like this, I'd like to implement my own. Could you provide some pointers/direction on the best way to extend Rebus with this functionality?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I see libraries like Rebus and MassTransit implement their own version of the Claim Check pattern. However, all of these typically involve modifying the DTO structure to support claim check, which in my view defeats the purpose. I believe claim check should be transient -- if a serialized payload size is greater than some configurable threshold, then instead of being sent as the message body, it should be stored in some configurable data store (e.g. S3, DynamoDB) and a claim check ID header should be added to the message.
On the receiving end, if the claim check header exists, pull data from that storage layer and deserialize it into the final strongly-typed DTO structure the consumer wants.
Because I do not see any available implementations that do claim check transparently like this, I'd like to implement my own. Could you provide some pointers/direction on the best way to extend Rebus with this functionality?
Beta Was this translation helpful? Give feedback.
All reactions