Slipstream 0.0.5

Slipstream

Fast, lean CQRS dispatcher with pipeline behaviors.

Slipstream is a lightweight alternative to MediatR focused on doing one thing well — dispatching requests through a pipeline to a single handler. No event publishing, no bloat, just clean request/response dispatching.

Features

• Request/response dispatching via IDispatcher
• Void request support (fire-and-forget style)
• Pipeline behaviors for cross-cutting concerns (logging, validation, transactions, etc.)
• Reflection-free hot path via cached generic wrappers
• No dependencies beyond Microsoft.Extensions.DependencyInjection.Abstractions

Installation

dotnet add package Slipstream

Quick Start

1. Define a request

// With a response
public record GetOrderById(int Id) : IRequest<Order>;

// Without a response
public record DeleteOrder(int Id) : IRequest;

2. Implement a handler

public class GetOrderByIdHandler : IRequestHandler<GetOrderById, Order>
{
    public Task<Order> Handle(GetOrderById request, CancellationToken cancellationToken)
    {
        // your logic here
        return Task.FromResult(new Order(request.Id));
    }
}

public class DeleteOrderHandler : IRequestHandler<DeleteOrder>
{
    public Task Handle(DeleteOrder request, CancellationToken cancellationToken)
    {
        // your logic here
        return Task.CompletedTask;
    }
}

3. Register with your DI container

// Scans the assembly and registers all handlers and the dispatcher
builder.Services.AddSlipstream(typeof(GetOrderByIdHandler).Assembly);

// Register behaviors manually in the order you want them to execute
builder.Services.AddTransient(typeof(IPipelineBehavior<,>), typeof(LoggingBehavior<,>));
builder.Services.AddTransient(typeof(IPipelineBehavior<,>), typeof(ValidationBehavior<,>));

Note: Behaviors are intentionally left to the consumer to register. Order matters — behaviors execute in registration order, so explicit control is by design.

4. Dispatch

public class OrdersController
{
    private readonly IDispatcher _dispatcher;

    public OrdersController(IDispatcher dispatcher)
    {
        _dispatcher = dispatcher;
    }

    public async Task<Order> Get(int id)
    {
        return await _dispatcher.Send(new GetOrderById(id));
    }
}

Pipeline Behaviors

Behaviors wrap handler execution and are ideal for logging, validation, exception handling, and transactions.

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 Task<TResponse> Handle(
        TRequest request,
        CancellationToken cancellationToken,
        RequestHandlerDelegate<TResponse> next)
    {
        _logger.LogInformation("Handling {Request}", typeof(TRequest).Name);
        var response = await next();
        _logger.LogInformation("Handled {Request}", typeof(TRequest).Name);
        return response;
    }
}

Behaviors execute in registration order, wrapping the handler like an onion:

Behavior1 -> Behavior2 -> Handler -> Behavior2 -> Behavior1

Why Not MediatR?

MediatR is excellent but carries features many projects don't need — notifications, polymorphic dispatch, and a growing surface area. Slipstream is for teams that want the request/pipeline pattern without the overhead.

License

MIT