Implementations of EIP message routing patterns
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
src Updating to release May 30, 2018
.gitattributes Create .gitattributes Feb 2, 2013
.gitignore UPdating tests Sep 25, 2017
Build.ps1 Fixing build Sep 25, 2017 add icon Dec 9, 2016
appveyor.yml Adding a build Sep 25, 2017
license.txt add mit license Dec 9, 2016
package_icon.png add icon Dec 9, 2016



Implementations of EIP message routing patterns for NServiceBus

Currently the patterns implemented include the routing slip. Planned are a true saga implementation (w/ compensating actions) and more.

Routing Slips

The Routing Slip pattern enables you to route a message to one or more destinations. Each step handles the message and forwards to the next step.

Forwarding is transparent to each handler, nor does each handler need to have any additional configuration for other steps.

To enable in each endpoint, configure routing slips in your EndpointConfiguration:


Then kick off the process by sending a message and including the list of destinations, either from an IPipelineContext inside a message handler or IMessageSession from your endpoint instance:

// From your endpoint instance
endpoint.Route(order, new[] {"Validate", "Fraud", "CreditCheck", "Process"});

// Inside a message handler
context.Route(order, new[] {"Validate", "Fraud", "CreditCheck", "Process"});

Each endpoint needs to include a handler for the message. Optionally, each endpoint can inspect/modify routing slip attachments:

context.Extensions.Get<RoutingSlip>().Attachments["FraudResult"] = "Declined";

Routing slip attachments are data that you share between different handlers in the route steps. As the message flows from step to step, the original raw transport message is passed through as-is.

That's all there is to it!


Route designed by Steven Lester from The Noun Project