Home/ Questions/Q 757537
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-14T15:22:29+00:00

I have read about the true messaging and that instead of sending payload on

  • 0

I have read about the true messaging and that instead of sending payload on the bus, it sends an identifier. In our case, we have a lot of legacy apps/services and those were designed to receive the payload of messages (xml) that is close to 4MB (close MSMQ limit). Is there a way for nService bus to handle large payload and persist messages automatically or another work-around, so that the publisher/subscriber services don’t have to worry neither about the payload size, nor about how to de/re-hydrate the payload?
Thank you in advance.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I’m not aware of any internal NServiceBus capability to associate extra data with a message out of band.

    I think you’re right on the mark – if the entire payload can’t fit within the limit, then it’s better to persist it elsewhere on your own and then passing an ID.

    However, it may be possible for you to design a message structure such that a message could implement an IHasPayload interface (which would perhaps incorporate an ID and a Type?), and then your application logic could have a common method for getting the payload given an IHasPayload message.

    • 0