What problem does it solve?
This Skill helps you design dependable, event-driven messaging in .NET so that background workflows and module-to-module communication remain consistent even under failures.
Core Features & Use Cases
- Wolverine-first messaging patterns: Set up transports, discover handlers, and use outbox/saga support to run event-driven code reliably.
- Transactional outbox reliability: Ensure events are only published after the database transaction commits, preventing dual-write inconsistencies.
- Choreography vs saga orchestration: Use event choreography for simple multi-step flows and sagas for complex workflows with compensation.
- Optional alternative with MassTransit: Use MassTransit where required, including consumers, endpoints, and outbox/saga concepts.
- Use Case: When an OrderCreated event is stored in one module, reliably trigger downstream notification and fulfillment logic in other modules without losing or duplicating events.
Quick Start
Load the messaging skill and configure Wolverine with RabbitMQ (or Azure Service Bus) plus a transactional outbox so published events are tied to successful database commits.