messaging

A transactional outbox in .NET ensures messages are published only after successful database transactions by integrating DbContext with your message bus, preventing data inconsistency from dual-writes. This Skill provides production-grade patterns for this setup.

Configuring Wolverine for RabbitMQ or Azure Service Bus involves an opinionated setup providing built-in outbox and saga support for mediator and messaging workflows. This approach offers a streamlined, MIT-licensed alternative for event-driven .NET services.

Saga orchestration is preferred over choreography for event-driven workflows when you need to model stateful sagas and explicit compensations across complex inter-service integration. This Skill provides guidance on when to apply each pattern.

Wolverine is recommended first for .NET asynchronous messaging due to its built-in outbox and MIT licensing, while MassTransit is offered as an alternative with specific commercial licensing considerations to evaluate before committing.

Setting up convention-based message handlers in .NET involves using cascading returns and explicit IMessageBus publishing for reliable event-driven communication. This Skill details these patterns and highlights anti-patterns to avoid during implementation.

Inter-service communication in .NET loses messages during transaction failures when dual-writes are used without a transactional outbox. Implementing outbox patterns with DbContext integration ensures messages are only published after successful transactions.