AxisCore.Mediator 1.0.1

AxisCore.Mediator

A high-performance, production-ready .NET library implementing the Mediator pattern. AxisCore.Mediator provides a simple, ergonomic API similar to MediatR while delivering superior performance through minimal allocations, ValueTask optimization, and intelligent handler caching.

Features

• High Performance: ValueTask-based, zero-allocation hot path with compiled delegate caching
• Multi-Targeting: Supports .NET 9, .NET 8, and .NET 6
• Simple API: Clean, intuitive interface similar to MediatR
• Pipeline Behaviors: Middleware-style request processing
• DI First: Seamless integration with Microsoft.Extensions.DependencyInjection
• Streaming Support: Built-in support for IAsyncEnumerable streaming responses
• Flexible Publishing: Multiple notification publishing strategies (parallel, sequential)
• Comprehensive Testing: Extensive unit and integration test coverage
• Production Ready: Thread-safe, cancellation-aware, with robust error handling

Installation

dotnet add package AxisCore.Mediator

Quick Start

1. Define a Request and Handler

using AxisCore.Mediator;

// Define a request
public class GreetingRequest : IRequest<string>
{
    public string Name { get; set; }
}

// Define a handler
public class GreetingRequestHandler : IRequestHandler<GreetingRequest, string>
{
    public ValueTask<string> Handle(GreetingRequest request, CancellationToken cancellationToken)
    {
        return new ValueTask<string>($"Hello, {request.Name}!");
    }
}

2. Register with DI

using Microsoft.Extensions.DependencyInjection;
using AxisCore.Mediator.DependencyInjection;

var services = new ServiceCollection();

// Auto-scan and register all handlers from the calling assembly
services.AddMediatorFromAssembly();

// Or scan specific assemblies
services.AddMediator(new[] { typeof(Program).Assembly });

var provider = services.BuildServiceProvider();

3. Send Requests

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

var response = await mediator.Send(new GreetingRequest { Name = "World" });
// Output: "Hello, World!"

Core Concepts

Requests and Handlers

Requests represent actions or queries. Handlers contain the logic to process them.

// Request with response
public class CreateOrderCommand : IRequest<OrderResult>
{
    public string CustomerId { get; set; }
    public decimal Amount { get; set; }
}

public class CreateOrderCommandHandler : IRequestHandler<CreateOrderCommand, OrderResult>
{
    public ValueTask<OrderResult> Handle(CreateOrderCommand request, CancellationToken cancellationToken)
    {
        // Business logic here
        return new ValueTask<OrderResult>(new OrderResult { OrderId = Guid.NewGuid() });
    }
}

// Usage
var result = await mediator.Send(new CreateOrderCommand { CustomerId = "123", Amount = 99.99m });

Notifications

Notifications are published to multiple handlers (pub/sub pattern).

// Define notification
public class OrderCreatedNotification : INotification
{
    public string OrderId { get; set; }
}

// Define handlers (multiple handlers can handle the same notification)
public class SendEmailHandler : INotificationHandler<OrderCreatedNotification>
{
    public ValueTask Handle(OrderCreatedNotification notification, CancellationToken cancellationToken)
    {
        // Send email logic
        return ValueTask.CompletedTask;
    }
}

public class UpdateInventoryHandler : INotificationHandler<OrderCreatedNotification>
{
    public ValueTask Handle(OrderCreatedNotification notification, CancellationToken cancellationToken)
    {
        // Update inventory logic
        return ValueTask.CompletedTask;
    }
}

// Usage
await mediator.Publish(new OrderCreatedNotification { OrderId = "ORD-123" });

Pipeline Behaviors

Pipeline behaviors wrap around request handlers, enabling cross-cutting concerns like logging, validation, and performance monitoring.

public class LoggingBehavior<TRequest, TResponse> : IPipelineBehavior<TRequest, TResponse>
    where TRequest : IRequest<TResponse>
{
    private readonly ILogger<LoggingBehavior<TRequest, TResponse>> _logger;

    public LoggingBehavior(ILogger<LoggingBehavior<TRequest, TResponse>> logger)
    {
        _logger = logger;
    }

    public async ValueTask<TResponse> Handle(
        TRequest request,
        RequestHandlerDelegate<TResponse> next,
        CancellationToken cancellationToken)
    {
        _logger.LogInformation("Handling {RequestName}", typeof(TRequest).Name);
        var response = await next();
        _logger.LogInformation("Handled {RequestName}", typeof(TRequest).Name);
        return response;
    }
}

// Register
services.AddTransient(typeof(IPipelineBehavior<,>), typeof(LoggingBehavior<,>));

Streaming Responses

For scenarios requiring streaming data:

public class GetLogsRequest : IStreamRequest<LogEntry>
{
    public DateTime FromDate { get; set; }
}

public class GetLogsHandler : IStreamRequestHandler<GetLogsRequest, LogEntry>
{
    public async IAsyncEnumerable<LogEntry> Handle(
        GetLogsRequest request,
        [EnumeratorCancellation] CancellationToken cancellationToken)
    {
        await foreach (var log in FetchLogsAsync(request.FromDate, cancellationToken))
        {
            yield return log;
        }
    }
}

// Usage
await foreach (var log in mediator.CreateStream(new GetLogsRequest { FromDate = DateTime.UtcNow.AddDays(-7) }))
{
    Console.WriteLine(log);
}

Configuration

Publishing Strategies

Control how notifications are published to multiple handlers:

services.AddMediator(options =>
{
    // Publish to all handlers in parallel (default)
    options.NotificationPublisherStrategy = NotificationPublisherStrategy.PublishParallel;

    // Or publish sequentially
    // options.NotificationPublisherStrategy = NotificationPublisherStrategy.PublishSequential;

    // Or stop on first exception
    // options.NotificationPublisherStrategy = NotificationPublisherStrategy.PublishSequentialStopOnException;
});

Service Lifetimes

Specify handler lifetimes:

// Transient (default)
services.AddMediatorFromAssembly(lifetime: ServiceLifetime.Transient);

// Scoped
services.AddMediatorFromAssembly(lifetime: ServiceLifetime.Scoped);

// Or manually register
services.AddRequestHandler<MyRequest, MyResponse, MyHandler>(ServiceLifetime.Scoped);

Built-in Behaviors

Logging Behavior

services.AddTransient(typeof(IPipelineBehavior<,>), typeof(LoggingBehavior<,>));

Performance Monitoring

services.AddTransient(typeof(IPipelineBehavior<,>), typeof(PerformanceBehavior<,>));

Validation

services.AddTransient(typeof(IPipelineBehavior<,>), typeof(ValidationBehavior<,>));

Performance

AxisCore.Mediator is designed for high-performance scenarios:

• ValueTask: Reduces allocations for synchronous or cached operations
• Handler Caching: Compiled delegates cached for fast resolution
• Minimal Allocations: Zero-allocation hot path for simple requests
• Concurrent Safe: Thread-safe handler resolution and caching

Benchmarks

Run your own benchmarks:

dotnet run --project benchmarks/AxisCore.Mediator.Benchmarks -c Release

Migration from MediatR

See MIGRATION.md for a detailed migration guide.

Key Differences:

• Handlers return ValueTask<T> instead of Task<T>
• Some MediatR-specific features may differ (see migration guide)

Documentation

• API Documentation
• Migration Guide
• Performance Guide
• Best Practices

Examples

See the samples directory for complete examples:

• Basic Usage

Contributing

Contributions are welcome! Please read CONTRIBUTING.md for details on our code of conduct and the process for submitting pull requests.

License

This project is licensed under the MIT License - see the LICENSE file for details.

Support

• Issues: GitHub Issues
• Discussions: GitHub Discussions

Acknowledgments

Inspired by MediatR by Jimmy Bogard. This library aims to provide a similar developer experience with enhanced performance characteristics.