https://github.com/jbogard/nservicebus.messagerouting

Implementations of EIP message routing patterns
https://github.com/jbogard/nservicebus.messagerouting

Last synced: about 1 month ago
JSON representation

Implementations of EIP message routing patterns

• Host: GitHub
• URL: https://github.com/jbogard/nservicebus.messagerouting
• Owner: jbogard
• License: mit
• Created: 2013-02-02T19:33:38.000Z (almost 12 years ago)
• Default Branch: master
• Last Pushed: 2024-07-09T21:38:56.000Z (6 months ago)
• Last Synced: 2024-11-09T03:58:22.927Z (about 2 months ago)
• Language: C#
• Size: 1.42 MB
• Stars: 41
• Watchers: 8
• Forks: 19
• Open Issues: 7
• Metadata Files:
  • Readme: README.md
  • License: license.txt

Awesome Lists containing this project

README

        
![Icon](https://raw.github.com/jbogard/NServiceBus.MessageRouting/master/package_icon.png)

NServiceBus.MessageRouting

==========================

*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.

![CI](https://github.com/jbogard/NServiceBus.MessageRouting/workflows/CI/badge.svg)

[![NuGet](https://img.shields.io/nuget/dt/NServiceBus.MessageRouting.svg)](https://www.nuget.org/packages/NServiceBus.MessageRouting) 

[![NuGet](https://img.shields.io/nuget/vpre/NServiceBus.MessageRouting.svg)](https://www.nuget.org/packages/NServiceBus.MessageRouting)

[![MyGet (dev)](https://img.shields.io/myget/nservicebus-messagerouting-ci/v/NServiceBus.MessageRouting.svg)](https://myget.org/gallery/nservicebus-messagerouting-ci)

Routing Slips

-------------

The [Routing Slip pattern](http://www.enterpriseintegrationpatterns.com/RoutingTable.html) 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.

    

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:

```c#

// 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:

```c#

context.Extensions.Get().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!

## Icon 

Route designed by Steven Lester from The Noun Project