Trellis.EntityFrameworkCore.Outbox 3.0.0-alpha.382

Trellis.EntityFrameworkCore.Outbox

Transactional outbox for Trellis: capture aggregate domain events into an EF Core table in the same transaction as the aggregate change, then relay them to your Trellis domain-event handlers after the commit succeeds — durable, at-least-once, in-process dispatch.

Installation

dotnet add package Trellis.EntityFrameworkCore.Outbox

Why

The default in-pipeline domain-event dispatch fires after the transaction commits, so a crash between commit and dispatch loses the events. The outbox closes that gap: each event is written atomically with the aggregate, survives a crash, and is re-dispatched by a background relay.

Quick Example

Three wiring points — the table, the capture interceptor, and the relay.

// Raise events from inside the aggregate, exactly as you do today.
public sealed record OrderPlaced(OrderId OrderId, DateTimeOffset OccurredAt) : IDomainEvent;

public sealed class Order : Aggregate<OrderId>
{
    public void Place(TimeProvider clock) =>
        DomainEvents.Add(new OrderPlaced(Id, clock.GetUtcNow()));
}

// 1. Map the outbox table (OnModelCreating).
protected override void OnModelCreating(ModelBuilder modelBuilder) =>
    modelBuilder.AddTrellisOutbox();

// 2. Add the capture interceptor where the context options are built.
options.UseNpgsql(connectionString)
       .AddTrellisInterceptors()
       .AddTrellisOutboxInterceptor();

// 3. Register the relay (plus your handlers) at the composition root.
services.AddTrellis(trellis => trellis
    .UseDomainEvents(typeof(Program).Assembly)     // handlers + IDomainEventPublisher
    .UseEntityFrameworkUnitOfWork<AppDbContext>()
    .UseOutbox<AppDbContext>(o =>
    {
        o.PollInterval = TimeSpan.FromSeconds(2);
        o.BatchSize = 100;
        o.MaxAttempts = 10;
    }));

Now await dbContext.SaveChangesAsync(ct) commits the OrderPlaced row in the same transaction as the order; the relay re-dispatches it to IDomainEventHandler<OrderPlaced> after the commit.

Prefer raw DI? Call services.AddTrellisOutbox<AppDbContext>() instead of the UseOutbox builder slot — the table and interceptor wiring (steps 1–2) are identical.

Key Features

• Atomic capture — one TrellisOutboxMessages row per uncommitted domain event, written in the same SaveChanges transaction as the aggregate. State and notifications commit together or not at all.
• Single dispatch path — when the outbox is enabled the capture interceptor clears the aggregate's events inside the commit, so the in-pipeline dispatch sees none and the durable relay is the one dispatcher.
• At-least-once delivery — a background relay drains pending rows in Sequence order and re-dispatches each event through IDomainEventPublisher, retrying infrastructure failures up to MaxAttempts.
• Crash-safe — a failed save rolls back the captured rows and preserves the in-memory events for retry; a crash after commit re-delivers on the next drain. Handlers must be idempotent.

Integration events

Translate internal domain events into stable external contracts by handling the domain event and adding an IIntegrationEvent to the scoped collector:

public sealed record OrderPlacedIntegrationEvent(Guid OrderId, DateTimeOffset OccurredAt)
    : IIntegrationEvent;

public sealed class OrderPlacedTranslator(IIntegrationEventCollector collector)
    : IDomainEventHandler<OrderPlaced>
{
    public ValueTask HandleAsync(OrderPlaced domainEvent, CancellationToken cancellationToken)
    {
        collector.Add(new OrderPlacedIntegrationEvent(domainEvent.OrderId.Value, domainEvent.OccurredAt));
        return ValueTask.CompletedTask;
    }
}

The relay drains IIntegrationEventCollector after dispatching each domain event and publishes through IIntegrationEventPublisher. The default publisher fans out in-process; replace it with a broker adapter for cross-service delivery. Delivery is at least once, so consumers must be idempotent on business identity.

Delivery & Serialization Notes

• The guarantee is at-least-once delivery, not handler success: per the IDomainEventHandler<TEvent> contract the publisher logs and swallows handler exceptions, so a failing handler does not retry — only infrastructure failures do.
• Events are serialized with the default System.Text.Json options. Trellis value objects that carry a [JsonConverter] attribute round-trip; use a nullable transport (not Maybe<T>) for optional event payload members.

Documentation

• Full documentation
• API Reference

Part of Trellis

This package is part of the Trellis framework.