notification-handlers

MediatR notification handlers dispatch domain events after successful persistence to trigger multiple independent responders. This ensures consistent side effects like emails, analytics, and audit trails without risking partial updates from failed database transactions.

Trigger multiple handlers for a single domain event by implementing several INotificationHandler implementations for the same event. MediatR supports parallel or sequential execution of these independent responders to coordinate consistent reactions across your system.

Dispatching domain events after saving changes maintains data integrity and avoids partial updates. If events fire before persistence and the transaction fails, downstream side effects like emails or analytics would react to data that does not exist.

Make MediatR notification handlers idempotent by using a domain event base type and a post-commit publisher designed for reliability. This pattern ensures that duplicate event processing does not cause repeated side effects like duplicate audit trails or analytics entries.

Yes, MediatR notifications support cross-service side effects such as emails, analytics, and audit trails by attaching multiple independent responders to a single domain event within a domain-driven design architecture.

Automatically publish domain events in a domain-driven design by implementing an interceptor-based dispatcher. This pattern automatically dispatches events defined on your aggregates through MediatR after changes are successfully saved.