Skip to main content

Performance Notification Operations

Summary​

Performance does not call Notification synchronously. Seven lifecycle contracts are published asynchronously and recognized by Notification.

Safe checks distinguish: Performance state commit, outbox intent, publication outcome, consumer receipt/idempotency, notification intent, and channel-delivery outcome. A successful Performance request does not guarantee end-user delivery.

Notification owns duplicate suppression, templates, preferences, recipient resolution, bounded channel attempts, and delivery evidence. Performance support should escalate after identifying the failing boundary, without collecting message content or recipient details.

Safety and confirmation boundary​

No production command, secret, configuration value, internal address, infrastructure detail, direct data change, or replay instruction is provided. Production ownership, approvals, service objectives, alerting, and recovery authority require confirmation.

Source References​

  • microservices/src/notification-service/Messaging/NotificationEventConsumer.cs
  • microservices/src/notification-service/Application/EventNotificationResolver.cs
  • microservices/src/notification-service/Application/NotificationDispatcher.cs

See Also​

Keywords​

  • Performance operations
  • Safe support guidance

Revision Information​

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