Api communication to another endpoint

[Fouad Roumieh]

Helpful information to include

Product name:NserviceBus

Version:6.4.0

Stacktrace:

Description: I'm using a .net core api that is supposed to communicate to another endpoint. Does the api needs to use the same Transport as the endpoint or it can be different?

[Hadi Eskandari]

Hi Fouad,

You're right, the endpoints need to have a similar configuration. This means you'll need the same transport and serialization between the communicating endpoints. For example, they both need to be on MSMQ Transport and using JSON serialization.

We do have a couple of workarounds for scenarios that you don't have control on both ends. Depending on behavior of your endpoints you can use the Transport Bridge or Wormhole Gateway. Have a look at the comparison table on this page which tells you which features are supported in which scenarios.

Hope this helps,

Hadi

[Simon Cropp]

Some clarifications. 

An endpoint can support multiple deserializers https://docs.particular.net/nservicebus/serialization/#specifying-additional-deserializers

and multiple endpoints can be hosted in the same process https://docs.particular.net/samples/hosting/multi-hosting/