Skip to main content

Notification Domain Events

Summary​

No domain event exists. The Notification Service has no aggregate root, no domain-event collection, no event raiser and no dispatch of internal events.

Audience​

Engineers, architects, QA and support.

Reference Content​

The verified reference material for this topic is set out in the sections below.

Inventory​

Domain eventCount
Declared domain events0

Verified absence​

  • No entity exposes a domain-event collection, a raise method or a clear method.
  • No base entity, aggregate-root type or marker interface exists — the seven persistence entities are plain classes with public settable properties.
  • No domain-event dispatcher, mediator or in-process handler is registered.
  • No save-time hook collects and publishes events, because the persistence context does not override save behavior.

This differs from several other extracted services in this platform, which model typed aggregates that raise domain events and relay them through an outbox.

What replaces it​

State transitions are applied by direct mutation inside the dispatcher and the API handlers. When a message moves to sent, failed or read, the code assigns the status, stamps the relevant timestamp and saves. Nothing is raised.

The append-only audit log serves the descriptive purpose a domain event stream would serve — it records that a stage occurred, with thirteen defined stages — but it is a persisted record written directly, not an event that anything subscribes to or reacts to.

Consequences​

Behavior that would conventionally attach to a domain event is inlined at the mutation site. Adding a reaction to a state change therefore means editing the dispatcher rather than subscribing a handler, and there is no in-process extension point.

Classification​

Not implemented.

Requires confirmation​

Whether a domain model with raised events is planned for this service requires confirmation.

See Also​

Keywords​

  • Notification database
  • Domain Events
  • Draft database documentation

Source References​

  • microservices/src/notification-service/Domain/NotificationEntities.cs
  • microservices/src/notification-service/Application/NotificationDispatcher.cs
  • microservices/src/notification-service/Api/NotificationEndpoints.cs

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-21
  • Review cycle: Quarterly