We don't support the concept of "time to be processed" for messages

[udidahan]

trafficstars

One of the scenarios I use to describe the use of sagas is where we're integrating with external parties like FedEx for shipping. I describe the use of a timeout in the saga so that the overall process doesn't get stuck waiting for a response. When the timeout fires, the saga would then send a message to some other shipper (UPS/DHL). The problem that comes up is what happens if FedEx does actually end up shipping after sending a message to the other shipper.

Idea for a solution: When sending the first messages to FedEx, make it possible to specify a "time to be processed" - like a TTBR, but higher level. When an endpoint is about to process a message, it checks to see if its "time to be processed" has already passed and, if so, doesn't process it.

Some open questions: Should a message being intentionally discarded be audited? If so, how (if at all) would we indicate that it wasn't actually processed on purpose?