MNW #030: How To Publish MediatR Notifications In Parallel

Read time: 4 minutes

A big thank you to our sponsors who keep this newsletter free to the reader:

This week's issue is sponsored by Rebus Pro. Rebus Pro is the perfect one-up for serious Rebus users - use Fleet Manager to get Slack alerts when something fails, and retry dead-lettered messages with a click of the mouse.

And by Uno Platform. Uno Platfrom is a free and open-source development platform that allows you to build single codebase applications for Windows, iOS, Android, WebAssembly, macOS, and Linux with C# and XAML. Easily create applications that look and feel native to each platform without having to rewrite your codebase from scratch.

MediatR is a popular library with a simple mediator pattern implementation in .NET.

Here's a definiton taken from MediatR's GitHub: "In-process messaging with no dependencies."

With the rise in popularity of the CQRS pattern, MediatR became the go-to library to implement commands and queries.

However, MediatR also has support for the publish-subscribe pattern using notifications. You can publish an INotification instance and have multiple subscribers handle the published message.

Until recently, the handlers subscribing to an INotification message could only execute serially, one by one.

In this week's newsletter, I'll show you how to configure MediatR to execute the handlers in parallel.

How Publish-Subscribe Works With MediatR

Before I talk about notification publishing strategies, let's see how publish-subscribe works with MediatR.

You need a class implementing the INotification interface:

Then you need a respective INotificationHandler implementation:

And then you simply publish a message using either IMediator or IPublisher. I prefer using the IPublisher because it's more expressive:

MediatR will invoke all the respective handlers.

Introducing Notification Publisher Strategies

Before MediatR v12, the publishing strategy would invoke each handler individually.

However, there's a new interface INotificationPublisher controlling how the handlers are called.

The default implementation of this interface is ForeachAwaitPublisher:

But now you can also use the TaskWhenAllPublisher:

Here's a comparison between these two strategies.

ForeachAwaitPublisher:

Invokes each handler one by one
Fails when an exception occurs in one of the handlers

TaskWhenAllPublisher:

Invokes all the handlers at the same time
Executes all the handlers regardless of one of them throwing an exception

If you store the task returned by TaskWhenAllPublisher you can access the Task.Exception property, which will contain an AggregateException instance. You can then implement more robust exception handling.

Configuring MediatR Notification Publishing Strategy

How do we configure which INotificationPublisher strategy MediatR will use?

There's a new way to apply configuration options when calling the AddMediatR method.

You supply an Action<MediatRServiceConfiguration> delegate and configure the MediatRServiceConfiguration instance.

If you want to use the TaskWhenAllPublisher strategy, you can either:

Provide a value for the NotificationPublisher property
Specify the strategy type on the NotificationPublisherType property

You can also implement a custom INotificationPublisher instance and use your own implementation instead.

How Is This Useful?

Being able to run notification handlers in parallel provides a significant performance improvement over the default behavior.

However, note that all handlers will use the same service scope.

If you have service instances that don't support concurrent access you may run into problems.

Unfortunately, one such service instance is the EF Core DbContext.

In any case, I think this is a great addition to the already amazing MediatR library.

That's all for today.

See you next week.

Whenever you're ready, there are 3 ways I can help you 🎁

To access to all of the source code that I use in my YouTube videos support me on Patreon
For more practical & in-depth coding examples subscribe to my YouTube channel
Promote yourself to 12.000+ subscribers by sponsoring this newsletter (booked out 2 months)

P.S. Did you watch my video about Supabase? 👇

Supabase Crash Course For .NET Developers

You received this email because you subscribed to our list. You can unsubscribe at any time.

Dragise Cvetkovica 2, Niš, 18000, Serbia

MNW #030: How To Publish MediatR Notifications In Parallel

MNW #030: How To Publish MediatR Notifications In Parallel

How Publish-Subscribe Works With MediatR

Introducing Notification Publisher Strategies

Configuring MediatR Notification Publishing Strategy

How Is This Useful?

Older messages

MNW #029: Creating Data-Driven Tests With xUnit

MNW #028: Using Multiple EF Core DbContexts In a Single Application

MNW #027: How To Apply Functional Programming In C#

MNW #026: Outbox Pattern For Reliable Microservices Messaging 📦

Milan's .NET Weekly Newsletter And You 🎁

You Might Also Like

eBook: Software Supply Chain Security for Dummies

The 5 biggest AI prompting mistakes

An interactive tour of Go 1.24

Spyglass Dispatch: Bromo Sapiens

The $1.9M client

⚙️ Federal data centers

Post from Syncfusion Blogs on 01/15/2025

The Sequence Engineering #469: Llama.cpp is The Framework for High Performce LLM Inference

3 Actively Exploited Zero-Day Flaws Patched in Microsoft's Latest Security Update

The Sequence Engineering #469: Llama.cpp is The Framework for High Performce LLM Inference