Skip to main content

LMS Notification Operations

Summary​

Training does not call Notification Service directly. Notification independently subscribes to recognized Training event names, while Training publication remains unconfirmed.

Reference Content​

Operational evidence can distinguish contract definition, outbox staging, processor availability, broker publication, consumer recognition, duplicate suppression, and delivery outcome. These are separate states.

Notification owns its consumer, processed-event ledger, intent resolution, and delivery attempts. Training owns lifecycle staging. Relay ownership, requeue ceiling, templates, alerting, and end-to-end delivery objectives Require confirmation.

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/Program.cs
  • microservices/src/notification-service/Messaging/NotificationEventConsumer.cs
  • microservices/src/training-service/Program.cs

See Also​

Keywords​

  • LMS operations
  • LMS Notification Operations

Revision Information​

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