MitMediator 6.0.0

MitMediator

Fast mediator for handling requests, commands, notifications, and streams with ValueTask and ordered pipelines

✨ Features

• Supports IRequest<TResponse> and IRequest (void-style)
• Custom handlers via IRequestHandler<,> and IRequestHandler<>
• Supports both ValueTask (for modern, efficient handlers) and Task (for compatibility with MediatR-style handlers)
• Enables middleware-style pipelines using IPipelineBehavior<TRequest, TResponse>. A pipeline behavior can be defined for all or specific request types.
• Supports INotificationHandler with serial and parallel publishing
• Ordered execution of pipeline behaviors
• Simple registration through AddMitMediator() or assembly scanning
• Supports IStreamRequestHandle and IStreamPipelineBehavior

🚀 Getting Started

Installation

dotnet add package MitMediator -v 6.0.0

Example Usage

Simple application with PingRequest, PingRequestHandler and two behaviors.

using Microsoft.Extensions.DependencyInjection;
using MitMediator;


var services = new ServiceCollection();
services
    .AddMitMediator(typeof(PingRequestHandler).Assembly)
    .AddTransient(typeof(IPipelineBehavior<,>), typeof(HeightBehavior<,>))
    .AddTransient(typeof(IPipelineBehavior<,>), typeof(LowBehavior<,>));

var provider = services.BuildServiceProvider();
var mediator = provider.GetRequiredService<IMediator>();

//HeightBehavior: Handling PingRequest
//LowBehavior: Handling PingRequest
//PingRequestHandler: Pong
//LowBehavior: Handled PingRequest
//HeightBehavior: Handled PingRequest
string result = await mediator.SendAsync<PingRequest, string>(new PingRequest(), CancellationToken.None);

Console.WriteLine(result); //Pong result

public class PingRequest : IRequest<string> { }

public class PingRequestHandler : IRequestHandler<PingRequest, string>
{
    public ValueTask<string> HandleAsync(PingRequest request, CancellationToken cancellationToken)
    {
        Console.WriteLine("PingRequestHandler: Pong");
        return ValueTask.FromResult("Pong result");
    }
}

public class LowBehavior<TRequest, TResponse> : IPipelineBehavior<TRequest, TResponse> where TRequest : IRequest<TResponse>
{
    public async ValueTask<TResponse> HandleAsync(TRequest request, IRequestHandlerNext<TRequest, TResponse> next, CancellationToken cancellationToken)
    {
        Console.WriteLine($"LowBehavior: Handling {typeof(TRequest).Name}");
        var result = await next.InvokeAsync(request, cancellationToken);
        Console.WriteLine($"LowBehavior: Handled {typeof(TRequest).Name}");
        return result;
    }
}

public class HeightBehavior<TRequest, TResponse> : IPipelineBehavior<TRequest, TResponse> where TRequest : IRequest<TResponse>
{
    public async ValueTask<TResponse> HandleAsync(TRequest request, IRequestHandlerNext<TRequest, TResponse> next, CancellationToken cancellationToken)
    {
        Console.WriteLine($"HeightBehavior: Handling {typeof(TRequest).Name}");
        var result = await next.InvokeAsync(request, cancellationToken);
        Console.WriteLine($"HeightBehavior: Handled {typeof(TRequest).Name}");
        return result;
    }
}

To use Task instead of ValueTask, use MitMediator.Tasks namespase.

🔁 Migrating from MediatR

You can reuse your existing handlers with minimal modifications — just update the namespaces and registration calls

1. Add the MitMediator package dotnet add package MitMediator -v 6.0.0
2. In your request files, replace the namespace MediatR with MitMediator
3. In your request handler files, replace the namespace MediatR with MitMediator (andMitMediator.Tasks for Task result)
4. Update your dependency injection setup: replace .AddMediatR(...) with .AddMitMediator()
5. If you're implementing INotificationHandler, use ValueTask instead of Task
6. If you're implementing IPipelineBehavior, use ValueTask instead of Task and IRequestHandlerNext<TRequest, TResponse> instead of RequestHandlerDelegate<TResponse>. Use next.InvokeAsync(request, cancellationToken) for next pipe
7. For handlers with void result, use Task<Unit> instead of Task (return Unit.Value)
8. (Optional) Change all mediator.Send(request, ct) to mediator.SendAsync<TRequset, TResponse>(request, ct) (or mediator.Send<TRequset, TResponse>(request, ct) for Task result)
9. Build and run your project — you’re all set!

Use SendAsync<TRequset, TResponse>(request, ct) for best performance or Send(request, ct) for backward compatibility with MediatR-style semantics

MitMediator is designed to feel familiar for those coming from MediatR. Core concepts like IRequest, IRequestHandle, and pipeline behaviors are preserved — but with a cleaner interface and support for ValueTask out of the box.

🔍 Comparison: MitMediator vs. MediatR

Performance

Features

🧪 Testing

This project includes comprehensive unit tests with 100% code coverage. All tests are included in the repository

🧩 Extensions

MitMediator.AutoApi - automatic creation of API endpoints for requests

📜 License

MIT