Wolverine

WolverineFx is a .NET runtime for command execution and message handling. One mental model covers many use cases: a method handles a message; the rest is just where the message comes from and what happens after it succeeds.

• In-process mediator — invoke a command, run a handler. Lower ceremony than MediatR.
• Local message bus — fire-and-forget across in-memory queues with optional durability.
• Distributed messaging — same handler model, fronted by RabbitMQ, Azure Service Bus, SQS/SNS, Kafka, NATS, Pulsar, MQTT, Redis, GCP Pub/Sub, PostgreSQL, SQL Server, etc.
• HTTP endpoints — WolverineFx.Http exposes methods as ASP.NET Core endpoints with the same conventions.
• Durable messaging — inbox/outbox on top of Marten, EF Core, or RavenDb for transactional consistency.
• Sagas / process managers — long-running stateful workflows.

CQRS and event sourcing are one thing Wolverine pairs well with (via Marten), but most features apply equally to plain command/event-driven services, modular monoliths, vertical-slice web apps, background workers, and ETL pipelines. Do not assume a Wolverine question implies event sourcing.

When agent context is tight