Messaging

codewithmukesh/dotnet-claude-kit/skills/messaging

by codewithmukesh23300897f4d1No license754 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 2 months ago

Asynchronous messaging patterns for .NET applications. Covers Wolverine and MassTransit, outbox pattern, saga and choreography, and broker configuration for RabbitMQ and Azure Service Bus. Load this skill when implementing event-driven communication, background processing, module-to-module messaging, or when the user mentions "Wolverine", "MassTransit", "message bus", "RabbitMQ", "Azure Service Bus", "event", "publish", "consumer", "outbox", "saga", "integration event", "queue", or "pub/sub".

Instructions onlySoftware Development
AI-generated overview

Guidance for implementing asynchronous messaging in .NET apps with Wolverine and MassTransit, including outbox, sagas and brokers.

What it does
This skill provides reference patterns and code examples for asynchronous messaging in .NET applications. It covers Wolverine and MassTransit setup, publishing and consuming events, the transactional outbox pattern, sagas versus choreography, and broker configuration for RabbitMQ and Azure Service Bus. It also lists anti-patterns and a decision guide for choosing approaches. It is instructions only and produces no files or scripts.
When to use it
Use it when implementing event-driven communication, background processing or module-to-module messaging in .NET. It is also relevant when working with Wolverine, MassTransit, RabbitMQ, Azure Service Bus, outbox, sagas, queues or pub/sub.
Requirements
No scripts or bundled assets; the agent needs no tools beyond itself. The guidance assumes a .NET project with Wolverine or MassTransit, EF Core, and a message broker such as RabbitMQ or Azure Service Bus, plus any credentials and network access those services require.

Messaging

Core Principles

  1. Wolverine is the recommended default — MIT licensed, combines mediator + messaging in one library with built-in outbox, saga support, and convention-based handlers. MassTransit is an alternative but requires a commercial license from v9.
  2. Outbox pattern for reliability — Always use the transactional outbox to ensure messages are published only when the database transaction succeeds.
  3. Choreography for simple flows, saga for complex — If a workflow has 2-3 steps, use event choreography. If it has compensating actions or complex state, use a saga.
  4. Messages are contracts — Put message types in a shared contracts project. Keep them as simple records with primitive types.

Patterns

Wolverine Setup

csharp
// Program.csbuilder.Host.UseWolverine(opts =>{    // Auto-discover handlers from this assembly    opts.Discovery.IncludeAssembly(typeof(Program).Assembly);
    // RabbitMQ transport    opts.UseRabbitMq(rabbit =>    {        rabbit.HostName = "localhost";        // Or from configuration:        // rabbit.HostName = builder.Configuration["RabbitMq:Host"]!;    })    .AutoProvision()   // Create queues/exchanges automatically    .AutoPurgeOnStartup(); // Dev only — clear queues on startup
    // Enable transactional outbox with EF Core    opts.Services.AddDbContextWithWolverineIntegration<AppDbContext>(x =>        x.UseNpgsql(builder.Configuration.GetConnectionString("Default")));
    opts.Policies.AutoApplyTransactions(); // Wrap handlers in DB transactions});

Why: UseWolverine() registers handler discovery, transport, and outbox in one place. AutoProvision() eliminates manual broker setup during development.

Publishing Events

Wolverine supports two publishing styles: cascading messages (return values) and explicit publishing.

csharp
// Message contract (in shared Contracts project)public record OrderCreated(Guid OrderId, string CustomerId, decimal Total, DateTimeOffset CreatedAt);
// Style 1: Cascading messages — return the event from the handler// Wolverine automatically publishes returned messages after the handler completes.public static class CreateOrder{    public record Command(string CustomerId, List<OrderItem> Items);    public record Response(Guid OrderId, decimal Total);
    public static async Task<(Response, OrderCreated)> HandleAsync(        Command command, AppDbContext db, TimeProvider clock, CancellationToken ct)    {        var order = Order.Create(command.CustomerId, command.Items, clock.GetUtcNow());        db.Orders.Add(order);        await db.SaveChangesAsync(ct);
        var response = new Response(order.Id, order.Total);        var @event = new OrderCreated(order.Id, order.CustomerId, order.Total, order.CreatedAt);
        return (response, @event); // Both are published automatically    }}
csharp
// Style 2: Explicit publishing via IMessageBuspublic static class CreateOrder{    public record Command(string CustomerId, List<OrderItem> Items);    public record Response(Guid OrderId, decimal Total);
    public static async Task<Response> HandleAsync(        Command command, AppDbContext db, IMessageBus bus, TimeProvider clock, CancellationToken ct)    {        var order = Order.Create(command.CustomerId, command.Items, clock.GetUtcNow());        db.Orders.Add(order);        await db.SaveChangesAsync(ct);
        await bus.PublishAsync(new OrderCreated(            order.Id, order.CustomerId, order.Total, order.CreatedAt));
        return new Response(order.Id, order.Total);    }}

Why: Cascading messages (tuple return) are simpler and testable — the handler is a pure function. Use explicit IMessageBus when publishing is conditional or requires multiple events.

Consuming Events

Wolverine uses convention-based handlers — no interface, no base class. Just a Handle method with the message type as the first parameter.

csharp
// Notifications module — handles OrderCreated from Orders modulepublic static class OrderCreatedHandler{    public static async Task HandleAsync(        OrderCreated message, NotificationsDbContext db, ILogger logger, CancellationToken ct)    {        logger.LogInformation("Processing OrderCreated: {OrderId}", message.OrderId);
        var notification = new OrderNotification(message.OrderId, message.CustomerId);        db.Notifications.Add(notification);        await db.SaveChangesAsync(ct);    }}

Why: Convention-based handlers have zero ceremony. Wolverine discovers them by signature: any public method named Handle/HandleAsync/Consume/ConsumeAsync with the message type as the first parameter.

Transactional Outbox

Ensures messages are only published if the database transaction succeeds.

csharp
// 1. Register DbContext with Wolverine integrationbuilder.Host.UseWolverine(opts =>{    opts.Services.AddDbContextWithWolverineIntegration<AppDbContext>(x =>        x.UseNpgsql(builder.Configuration.GetConnectionString("Default")));
    opts.Policies.AutoApplyTransactions();});
// 2. DbContext — add Wolverine outbox tablespublic class AppDbContext(DbContextOptions<AppDbContext> options) : DbContext(options){    public DbSet<Order> Orders => Set<Order>();
    protected override void OnModelCreating(ModelBuilder modelBuilder)    {        // Wolverine inbox/outbox tables — required for transactional messaging        modelBuilder.AddIncomingWolverineMessageTable();        modelBuilder.AddOutgoingWolverineMessageTable();    }}

Why: AddDbContextWithWolverineIntegration + AutoApplyTransactions wraps every handler in a transaction that includes outbox writes. Messages are only sent after the transaction commits — no dual-write problem.

Saga (Stateful Orchestration)

Wolverine sagas use a Saga<T> base class with Start and Handle methods. Cascading messages drive the saga forward.

csharp
public record OrderSagaState(Guid Id){    public string? CustomerId { get; set; }    public bool PaymentReceived { get; set; }}
public class OrderSaga : Saga<OrderSagaState>{    public Guid Id { get; set; }
    // Start the saga when an OrderCreated event arrives    public static (OrderSagaState, ProcessPayment) Start(OrderCreated message)    {        var state = new OrderSagaState(message.OrderId)        {            CustomerId = message.CustomerId        };
        var command = new ProcessPayment(message.OrderId, message.Total);        return (state, command); // State is persisted, command is sent    }
    // Handle payment result    public CompleteOrder Handle(PaymentCompleted message)    {        PaymentReceived = true;        MarkCompleted(); // Ends the saga        return new CompleteOrder(Id);    }
    // Compensating action on failure    public CancelOrder Handle(PaymentFailed message)    {        MarkCompleted();        return new CancelOrder(Id);    }}

Why: Wolverine sagas use simple C# methods instead of a state machine DSL. Each handler returns cascading messages to drive the workflow. MarkCompleted() cleans up the saga state.

Alternative: MassTransit

MassTransit is a mature alternative with a commercial license requirement from v9+. Key API surface:

csharp
// Setupbuilder.Services.AddMassTransit(x =>{    x.SetKebabCaseEndpointNameFormatter();    x.AddConsumers(typeof(Program).Assembly);    x.UsingRabbitMq((context, cfg) =>    {        cfg.Host(builder.Configuration.GetConnectionString("RabbitMq"));        cfg.ConfigureEndpoints(context);    });});
// Publishingawait publishEndpoint.Publish(new OrderCreated(...), ct);
// Consuming — requires IConsumer<T> interfacepublic class OrderCreatedConsumer(AppDbContext db) : IConsumer<OrderCreated>{    public async Task Consume(ConsumeContext<OrderCreated> context)    {        var message = context.Message;        // Handle event...    }}
// Outboxx.AddEntityFrameworkOutbox<AppDbContext>(o =>{    o.UsePostgres();    o.UseBusOutbox();});
// Saga — uses MassTransitStateMachine<TState>public class OrderSaga : MassTransitStateMachine<OrderSagaState> { /* ... */ }

License note: MassTransit v9+ requires a commercial license for production use. Wolverine (MIT) is the recommended default for new projects.

Anti-patterns

Don't Publish Events Without Outbox

csharp
// BAD — if SaveChanges succeeds but Publish fails, data is inconsistentawait db.SaveChangesAsync(ct);await bus.PublishAsync(new OrderCreated(...));
// GOOD — use transactional outbox (messages are in the same transaction)// Configure AddDbContextWithWolverineIntegration() + AutoApplyTransactions()// Wolverine handles this automatically

Don't Put Complex Logic in Message Contracts

csharp
// BAD — behavior in a messagepublic record OrderCreated(Guid OrderId){    public decimal CalculateShipping() => /* logic */; // DON'T}
// GOOD — messages are pure datapublic record OrderCreated(Guid OrderId, string CustomerId, decimal Total, DateTimeOffset CreatedAt);

Don't Use Fire-and-Forget for Important Events

csharp
// BAD — no guarantee of delivery_ = Task.Run(() => bus.PublishAsync(new OrderCreated(...)));
// GOOD — await the publish (with outbox, this is transactional)await bus.PublishAsync(new OrderCreated(...));

Decision Guide

ScenarioRecommendation
Module-to-module communication (new project)Wolverine with events (MIT, free)
Module-to-module communication (existing MassTransit)MassTransit (commercial license required from v9)
Reliable event publishingTransactional outbox (both Wolverine and MassTransit support this)
Simple 2-3 step workflowEvent choreography
Complex workflow with compensationWolverine saga or MassTransit saga
Local development brokerRabbitMQ (via Docker or Aspire)
Production cloud brokerAzure Service Bus or RabbitMQ
Want single lib for mediator + messagingWolverine (replaces both Mediator and MassTransit)

Source and attribution

Source:codewithmukesh/dotnet-claude-kitinskills/messagingat commit2330089

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

More from codewithmukesh/dotnet-claude-kit

Wrap Up

codewithmukesh

Captures end-of-session work, pending tasks and learnings into a handoff file, and reloads it at session start.

Productivity & Workflow754updated 2 months ago

Workflow Mastery

codewithmukesh

Claude Code workflow mastery for .NET developers. Covers parallel execution with git worktrees, plan mode strategy, verification loops, auto-formatting hooks, permission setup for dotnet CLI, prompting techniques, subagent patterns, and context discipline — token budget management, MCP-first navigation, lazy loading, and subagent isolation — all adapted for the .NET ecosystem. Load this skill when setting up Claude Code for a .NET project, optimizing workflows, running parallel sessions, when context is running low or sessions feel sluggish, when exploring a large codebase efficiently, or when the user mentions "productivity", "workflow", "parallel", "worktree", "plan mode", "permissions", "hooks", "10x", "setup Claude Code", "speed up development", "context", "tokens", "budget", "running out of context", "too many files", or "large codebase". Inspired by tips from Boris Cherny (creator of Claude Code) and the Anthropic team.

Awaiting classification754updated 2 months ago

Vertical Slice

codewithmukesh

Guides .NET developers in structuring applications with Vertical Slice Architecture, covering feature folders, endpoint grouping and handler patterns.

Software Development754updated 2 months ago

Testing

codewithmukesh

Testing strategy for .NET 10 applications. Covers xUnit v3, WebApplicationFactory for integration tests, Testcontainers for real database testing, Verify for snapshot testing, and the AAA pattern. Load this skill when writing tests, setting up test infrastructure, reviewing test coverage, or when the user mentions "test", "xUnit", "WebApplicationFactory", "Testcontainers", "integration test", "unit test", "bUnit", "snapshot test", "Verify", "test coverage", "AAA pattern", "WireMock", or "FakeTimeProvider".

Awaiting classification754updated 2 months ago

Tdd

codewithmukesh

Guided test-driven development workflow for .NET 10 using xUnit v3, WebApplicationFactory, Testcontainers, and Verify snapshots. Follows the strict red-green-refactor cycle. Use when: "TDD", "test-driven", "let's TDD this", "red green refactor", "write the test first", or when building a feature with clear acceptance criteria.

Awaiting classification754updated 2 months ago

Spec

codewithmukesh

Turns a vague feature idea into an agreed, persisted specification file through structured questioning rounds.

Productivity & Workflow754updated 2 months ago