When receiving a command message we could automatically delete the databus blob. This could be done via a separate message that triggers the deletion of the blob if the transaction completes as the databus IO is most likely not part of the transaction.
It would be hard to do for events as we don't know how many subscribers there are. If there was a pipeline per receiver than we would have the ability to do some sort of ref counting but that would only work in environments that use subscription storage I think.
@ramonsmits You opened up a series of data bus improvement proposals. Would it make sense to collect those in one single platform dev issue and raise it to the awareness of the squad?
When receiving a command message we could automatically delete the databus blob. This could be done via a separate message that triggers the deletion of the blob if the transaction completes as the databus IO is most likely not part of the transaction.
It would be hard to do for events as we don't know how many subscribers there are. If there was a pipeline per receiver than we would have the ability to do some sort of ref counting but that would only work in environments that use subscription storage I think.