The databus currently just stores any kind of blob, small and huge. Databus properties are there to solve issues with tranport message size limitations.
If working on MSMQ than there is a 4MB restriction. A lot of blobs could still fit the message. If we reserve a specific size for headers and header growth (64KB for example) it still has lots of spare room.
Make the databus smarter so that it only uses it when there is no room in the message body for storing the data.
This makes both the sending and receiving more performant as we don't need to make additional roundtrips for the blobs.
@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?
The databus currently just stores any kind of blob, small and huge. Databus properties are there to solve issues with tranport message size limitations.
If working on MSMQ than there is a 4MB restriction. A lot of blobs could still fit the message. If we reserve a specific size for headers and header growth (64KB for example) it still has lots of spare room.
Make the databus smarter so that it only uses it when there is no room in the message body for storing the data.
This makes both the sending and receiving more performant as we don't need to make additional roundtrips for the blobs.