MassTransit Routing Slip Arguments, Variables, and Unit Testing

MassTransit includes Courier, a routing slip implementation for building reliable distributed transactions with compensation. In this episode, I show how arguments are passed into activities, how variables can allow reuse across activities, and how to write variables out of activities. I also cover how to create unit tests for activities, including end-to-end routing slip unit tests.

Sample Project:

MassTransit

Connect with me on Twitter:

Sponsor me on GitHub:

[ugochukwuumerie]

Hello, must the subscription to the event emitted by the routing slip be done using saga state machine or are there other mechanisms to subscribe to routing slip events? Thank you.

[valetrujilloNV]

This was a deep dive, thanks for the video Chris. At 3:18, why are there two separate new blocks both including the registrationid and why would the participantemailaddress be here? Is that not already available in the routing slip as a variable? I see why you would want to get the Amount and registrationid added to the variables, but that first block is a bit confusing. Thanks!

[matiascasag]

Hi Chris, thanks for creating MassTransit and for taking time to do these videos. I have a doubt about Activities. Shouldn't each activity be on a different Project/Process/Service? If that is the case, How could you register those activities that are in different Project/Process/Service?