Simple Bridge Usage

Component: Transport Bridge
NuGet Package: NServiceBus.Transport.Bridge (1-pre)

This is a Preview project
This page targets a pre-release version. Pre-releases are subject to change and samples are not guaranteed to be fully functional.

This sample shows how to bridge two different transports.

For this sample to work without installing any prerequisites, all endpoints use the LearningTransport. To demonstrate that it can still bridge different transports, the LearningTransport on one side of the bridge is configured to store messages in a different location on disk.


The sample starts by sending a message from one endpoint, LeftSender, to another, RightReceiver. RightReceiver then replies with an OrderResponse message. LeftSender handles this message and publishes an OrderReceived message which is handled by another endpoint, LeftReceiver, as well as RightReceiver.

Here is a diagram of the message flow:

graph LR A[LeftSender] --> C[[BRIDGE]] B[LeftReceiver] --> C C --> D[RightReceiver] subgraph Transport A A B end subgraph Transport B D end

The projects are named this way to indicate which side of the bridge they exist. LeftSender and LeftReceiver are on one side of the bridge and RightReceiver is on the other. Both sides use the LearningTransport but RightReceiver uses a separate file location, which the sample does to mimic a separate transport than the one used by LeftSender and LeftReceiver.

The transport on either side can be modified to any supported transport. This also requires updating the bridge configuration (described later) but does not require any changes to endpoints on the other side of the bridge. For example, if RightReceiver is changed to use the RabbitMQ transport, no changes are required to either LeftSender or LeftReceiver; only the bridge configuration needs to be updated to use the new transport for the corresponding endpoint.

Here is a description of each project.


The project that references NServiceBus.Transport.Bridge and contains configuration to bridge the two transports.


The shared message contracts used by all endpoints. It also includes a helper class to find the storage location for the LearningTransport.


  • Launches the message flow by sending a PlaceOrder command message to RightReceiver.
  • Receives and handles OrderResponse messages.
  • Publish an OrderReceived message.


  • Receives and handles PlaceOrder commands and replies with an OrderResponse message.
  • Receives and handles OrderReceived events.


  • Receives and handles OrderReceived events.

Code walk-through

The sample uses the LearningTransport on both sides of the bridge. To simulate two different transports, the location on disk for the LearningTransport on the right side of the bridge is configured to use a different location on disk.

var learningTransportDefinition = new LearningTransport
    // Set storage directory and add the character '2' to simulate a different transport.
    StorageDirectory = $"{LearningTransportInfrastructure.FindStoragePath()}2"

Bridge configuration

Every endpoint that is available in the system must be configured in the bridge. This section shows different ways in which endpoints can be configured.


The LeftSender endpoint is an endpoint without subscriptions to any event and is the easiest to configure.

var learningLeft = new BridgeTransport(new LearningTransport());


The LeftReceiver endpoint is a subscriber to LeftSender, but it does not need to cross the bridge. That is, the bridge does not need to know about the LeftReceiver endpoint; no configuration is necessary.


The RightReceiver endpoint is configured as a new endpoint and the event Messages.Events.OrderPlaced is registered on the publisher, LeftReceiver, using the fully-qualified name. This is how events are registered if a message assembly cannot be shared with the bridge.

var rightReceiver = new BridgeEndpoint("Samples.Bridge.RightReceiver");
rightReceiver.RegisterPublisher("OrderReceived", "Samples.Bridge.LeftSender");

If an event assembly can be referenced directly by the bridge, the events can be registered by type, as described in documentation, to prevent typing mistakes. Registering by type is possible in this sample, as the Shared assembly has no references to any version of NServiceBus and message types are registered using conventions. For demo purposes the name was added as a string.

Add endpoints to bridge configuration

The last step is to register all the configured transports with the bridge itself


Migrating an endpoint

As an exercise, it is possible to move the LeftReceiver to yet another transport. With the learning transport, this is configured by specifying a separate file location, similar to how the RightReceiver is configured.

The bridge also must be configured so that a new BridgeTransport is added with the already existing leftReceiver on the new BridgeTransport. The end result looks like this:

graph LR A[LeftSender] --> C[[BRIDGE]] B[LeftReceiver] --> C C --> D[RightReceiver] subgraph Transport A A end subgraph Transport B D end subgraph Transport C B end

Related Articles

  • Bridge
    Connect endpoints in a system that use different transports with the transport bridge.

Last modified