search

Particular / NServiceBus

Build, version, and monitor better microservices with the most powerful service platform for .NET
https://particular.net/nservicebus/
Other
2.09k stars 648 forks source link

Make TimeToBeReceived when having DataBus properties #3205

Closed ramonsmits closed 8 years ago

ramonsmits commented 8 years ago

When messages have Databus properties and no TimeToBeReceived is set this basically indicates that the databus blobs can never be purged as the TTL will never expire.

By making TimeToBeReceived required for messages with databus properties it is forcing message designers to think about databus blob expiration/purging policy.

andreasohlund commented 8 years ago

I would propose that we introduce a databus storagage specific "max time" instead. Kind of similar to the "max 7 days" that ASB has for messages in its queues?

ramonsmits commented 8 years ago

@andreasohlund I like that idea. That could mean that it its lifespan can be longer than the TTBR of the message which could be inline with archive policy for audit messages.

timbussmann commented 8 years ago

since TTBR doesn't work well with MSMQ, this doesn't seem to be a valid option? Should we close this issue and discuss possible solutions in the pdev issue you raised @ramonsmits ?

ramonsmits commented 8 years ago

@timbussmann The reasoning that because MSMQ has unexpected TTBR behavior is more of a concern to MSMQ.

The reason for this issue is the abilty to to controlled purged of databus blobs. I do think now that explicitly setting the TTBR value suggestion is not a good solution for that and that it should be solved in another way and that concern is addresses in the platform dev issue so I'm fine with closing this.

timbussmann commented 8 years ago

and that it should be solved in another way and that concern is addresses in the platform dev issue

:+1: closing this then