Once you start doing in-process request & event dispatching, you’ll soon want to move out of process so you can isolate work from the caller/invoker. This is often times the next logical step if you’re using MediatR for commands and especially for events/notifications. Here’s how you can do use the same paradigm for in-process and out-of-process using Brighter and RabbitMQ.

Brighter:
https://github.com/BrighterCommand/Brighter

Blog:
https://codeopinion.com/moving-work-out-of-process-using-brighter-and-rabbitmq/

Why Use MediatR?
https://youtu.be/yhpTZDavtsY

🔔 Subscribe: https://www.youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw?sub_confirmation=1

💥 Join this channel to get access to source code, demos, and slides!
https://www.youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw/join

📝 Blog: https://codeopinion.com

📚 Book Recommendations

Domain-Driven Design
https://amzn.to/2QwG8sb

Patterns of Enterprise Application Architecture
https://amzn.to/3d8kMJj

Refactoring: Improving the Design of Existing Code
https://amzn.to/2NVdP5Q

Monolith to Microservices: Evolutionary Patterns to Transform Your Monolith
https://amzn.to/3srUuZ6

RESTful Web Clients: Enabling Reuse Through Hypermedia
https://amzn.to/3d8Q96B

0:00 Intro
0:22 In-Process Example
2:25 Brighter
3:25 Out-of-Process
6:38 Summary

CodeOpinon: https://codeopinion.com
Twitter: https://twitter.com/codeopinion

#rabbitmq #softwarearchitecture #dotnet

#rabbitmq #softwarearchitecture #dotnet #brighter