Round of applause. Great stuff, the higher level domain stuff is super useful to better understand how to fit these components together. And a bonus gnat kill :P
Thank you for these great tutorials! Did you get to the bottom of why allocate-inventory_compensate and allocate-inventory_execute have underscores? You mention it in this video.
I want to say backwards compatibility, changing it would likely break existing applications that have formatted the queue names for activities on their own.
It might be more job than you feel it is worth but something you could do on Github is to create tags that makr the state of the code at the end of each episode. It might make it easier when troubleshooting something we've messed up while following along your code rather than to look at code that is updated and changed since then. That is, if you have commits from the end of each episode. Understand if that would be a pain though. Keep up the great work!
hi Chris, tks for these videos. they're very educational! I have a question which I hope you can address. in this example, you had used a routing slip to access an external service, then wrapped it with saga. at least that's what I think happened. feel free to correct if my assumption is wrong. anyway, my question was -- can we simply use the sagas to perform that or should the routing slip pattern be used? thanks again.
A routing slip activity is not required, you could use a regular consumer. The saga would need to send the command to the consumer, and then handle the event produced by the consumer signifying success/failure of the external service interaction.
Hi Chris, I've been searching without luck, is there's a way you can retry an activity within a routing slip? I tried using a retry policy in the ReceiveEndpoint but it's not working for me.
You should be able to use configurator.UseMessageRetry(r => r.Immediate(2)); (or whichever policy you want) on the receive endpoint. You may need to be on a recent version of MassTransit.
I test all the built-in activities using the NUnit test fixtures (in the TestFramework) github.com/MassTransit/MassTransit/blob/develop/tests/MassTransit.Tests/Courier/SingleActivityEvent_Specs.cs#L73 - that might give you some examples of how to test activities. The entire folder is full of tests.
Round of applause. Great stuff, the higher level domain stuff is super useful to better understand how to fit these components together. And a bonus gnat kill :P
Thank you for these great tutorials! Did you get to the bottom of why allocate-inventory_compensate and allocate-inventory_execute have underscores? You mention it in this video.
I want to say backwards compatibility, changing it would likely break existing applications that have formatted the queue names for activities on their own.
53:20 Clap, clap, clap!
Thanks for this tutorial Chris!
It might be more job than you feel it is worth but something you could do on Github is to create tags that makr the state of the code at the end of each episode. It might make it easier when troubleshooting something we've messed up while following along your code rather than to look at code that is updated and changed since then. That is, if you have commits from the end of each episode. Understand if that would be a pain though. Keep up the great work!
I'll take a look, I'm not sure I have commits from each episode, at least not the early ones.
hi Chris, tks for these videos. they're very educational! I have a question which I hope you can address. in this example, you had used a routing slip to access an external service, then wrapped it with saga. at least that's what I think happened. feel free to correct if my assumption is wrong. anyway, my question was -- can we simply use the sagas to perform that or should the routing slip pattern be used? thanks again.
A routing slip activity is not required, you could use a regular consumer. The saga would need to send the command to the consumer, and then handle the event produced by the consumer signifying success/failure of the external service interaction.
@@PhatBoyG ok tks ---
Hi Chris, I've been searching without luck, is there's a way you can retry an activity within a routing slip? I tried using a retry policy in the ReceiveEndpoint but it's not working for me.
You should be able to use configurator.UseMessageRetry(r => r.Immediate(2)); (or whichever policy you want) on the receive endpoint. You may need to be on a recent version of MassTransit.
Hi Chris, can we write unit tests for activities and how?
I test all the built-in activities using the NUnit test fixtures (in the TestFramework) github.com/MassTransit/MassTransit/blob/develop/tests/MassTransit.Tests/Courier/SingleActivityEvent_Specs.cs#L73 - that might give you some examples of how to test activities. The entire folder is full of tests.
APPLAUSE !!!