Skip to main content

Implement the mediator pattern using MassTransit

The mediator pattern is a behavioral design pattern used in software engineering. It defines an object that encapsulates how a set of objects interact

In object-oriented programming, programs often consist of many classes. As more classes are added to a program, especially during maintenance or refactoring, the problem of communication between these classes becomes complex. Direct communication between objects can lead to tight coupling, making the program harder to read, maintain, and change.

The mediator pattern introduces a mediator object that acts as an intermediary between interacting objects. Instead of direct communication, objects now communicate through the mediator. This reduces dependencies between objects and promotes loose coupling.

A popular way to implement the mediator pattern in .NET is through the popular MediatR library. But if you are already using Masstransit,  there is no need to introduce an extra dependency as Masstransit has built-in support for the Mediator pattern.

Similar to MediatR, the MassTransit mediator runs in-process and in-memory. The nice thing is that it builds further on the concepts you already use in MassTransit, like consumers, handlers, sagas, …

Let me show you a quick example on how to get started.

Configure our Mediator pipeline

First we should create a Consumer, we could implement the default IConsumer interface or the MediatorRequestHandler that further simplifies the implementation when using the MassTransit mediator:

We'll use the MediatorRequestHandler in this example:

Now we need to register this handler:

A typical reason to use the mediator pattern is to isolate specific behavior in separate classes. In MassTransit we can use the middleware feature for this. We first need to create our filter:

And then we can configure to apply this filter in our mediator pipeline:

Send a request through the Mediator

Now the configuration is done, the only thing left to do is to send a request through the pipeline. This can be done by injecting an IMediator instance and calling the SendRequest method:

More information

Mediator · MassTransit

MassTransit/Sample-Mediator: A sample solution with various projects showing how to use MassTransit's mediator (github.com)

jbogard/MediatR: Simple, unambitious mediator implementation in .NET (github.com)

Also have a look at the following video:

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...