📄️ Overview
Understand RCommon's unified event handling pipeline — IEventBus, IEventProducer, IEventRouter, and ISubscriber — and how to choose between in-process and broker transports.
📄️ Recipes
The six supported event-handling and transactional-outbox recipes in RCommon 3.2.0 — DDD with the RCommon outbox, broker-as-producer, broker-native outbox, transaction-script, no-unit-of-work, and in-process MediatR — each with wiring and diagrams.
📄️ In-Memory Events
Configure RCommon's in-process event bus with InMemoryEventBusBuilder, implement ISubscriber handlers, and publish events via IEventRouter or IEventBus directly.
📄️ Distributed Events
Extend RCommon event handling to message brokers with MassTransit or Wolverine, mixing transports in one app while keeping ISubscriber handler code broker-agnostic.
📄️ Transactional Outbox
Guarantee at-least-once event delivery using the transactional outbox pattern with MassTransit EF Core outbox or Wolverine's EF Core transaction integration.
📄️ Outbox Producer/Processor Topology
How RCommon's built-in persistence outbox dispatches and marks events across multiple hosts, and why producer-only hosts must set OutboxOptions.ImmediateDispatch = false for reliable cross-host delivery.
📄️ MediatR
Route RCommon events through MediatR's notification pipeline using MediatREventHandlingBuilder, with ISubscriber handlers unaware of MediatR internals.
📄️ MassTransit
Deliver RCommon events across service boundaries via MassTransit consumers, with fan-out publish or point-to-point send and transport-agnostic ISubscriber handlers.
📄️ Wolverine
Use Wolverine as an event transport in RCommon's event handling pipeline, registering ISubscriber handlers and choosing between fan-out publish or point-to-point send.