Wolverine Documentation

The Wolverine.EntityFrameworkCore project provides several key capabilities for integrating EF Core with Wolverine:

• Transactional Outbox: Atomic database changes and message publishing.
• Saga Persistence: Full CRUD support (load, insert, update, delete) for Sagas via EF Core.
• Multi-tenancy: Support for per-tenant DbContext creation using either connection strings or DbDataSource.
• Domain Event Publishing: Automatically scrapes and publishes domain events by inspecting entities within the EF Core ChangeTracker.
• Idempotency: Uses inbox tracking to ensure messages are processed exactly once.
• Code Generation: Uses specialized frames that compile into Wolverine's JIT-generated handler pipelines for high performance.

Wolverine supports advanced validation through integration with standard .NET libraries:

• FluentValidation: Use the full feature set of FluentValidation (rule builders, conditional rules, etc.) by following the integration guide.
• Data Annotations: Use standard .NET attributes like [Required], [Range], and others directly on your message types.

Compatibility

The WolverineFX.RabbitMQ transport is verified to work with LavinMQ with 100% protocol compatibility.

Health Monitoring

The RabbitMQ transport implements IBrokerHealthProbe. This allows monitoring tools (like CritterWatch) to perform non-destructive, point-in-time checks on the broker connection, including monitoring reconnect counts and TLS certificate expiry.

Wolverine.HTTP provides three primary ways to implement validation:

1. Explicit Validate() or ValidateAsync() methods: The recommended approach for complex logic (e.g., database lookups or IoC service usage). These methods return ProblemDetails or WolverineContinue.NoProblems.
2. Fluent Validation middleware: Available via the separate WolverineFx.Http.FluentValidation NuGet package.
3. Data Annotations: Can be used by explicitly configuring Data Annotations middleware within your Wolverine.HTTP application setup.

Wolverine supports Amazon SNS via the WolverineFx.AmazonSns package.

Important Limitations:

• No Request/Reply: Wolverine cannot support request/reply mechanics (IMessageBus.InvokeAsync<T>()) with SNS.
• Publish-Only: Due to the nature of SNS, Wolverine does not include listening functionality for this transport. To receive messages, you should forward SNS messages to an Amazon SQS queue and use the SQS transport to listen for them.

Partitioned Sequential Messaging is a feature designed to manage concurrency by guaranteeing sequential processing within specific groups of messages (e.g., messages related to the same business entity like an Order) while allowing parallel processing between different groups. This prevents race conditions and incorrect system states caused by simultaneous writes to the same entity or event stream.

Wolverine currently supports this for:

1. Purely local processing within the current process.
2. Partitioned publishing to external transports (like RabbitMQ or Amazon SQS) across a range of queues.
3. Partitioned processing of messages received from external transports within a single process.

Conjoined Multi-Tenancy is a mode for EF Core in Wolverine that enables shared-database tenancy. Unlike the 'DB-per-tenant' mode, conjoined mode uses a single database where multiple tenants coexist in the same tables, distinguished by a tenant_id column.

When an EF entity implements the ITenanted interface, Wolverine automatically handles:

• Mapping the tenant_id column.
• Binding a global query filter to the ambient Wolverine tenant.
• Stamping the tenant ID on inserts.
• Rejecting cross-tenant writes.

This mode is a sibling to the existing AddDbContextWithWolverineManagedMultiTenancy (DB-per-tenant) and they are mutually exclusive per DbContext.

You can implement the IHttpAware interface on your response types to automatically apply metadata and HTTP runtime behavior (like status codes and headers) to any endpoint that returns that type. This ensures that your custom types are correctly reflected in exported OpenAPI documentation.

public record CreationResponse([StringSyntax("Route")] string Url) : IHttpAware
{
    public static void PopulateMetadata(MethodInfo method, EndpointBuilder builder)
    {
        builder.RemoveStatusCodeResponse(200);
        // ... logic to add 201 status code and type
    }

    void IHttpAware.Apply(HttpContext context)
    {
        context.Response.Headers.Location = Url;
        context.Response.StatusCode = 201;
    }
}