Skip to main content

LMS Runtime Overview

Summary​

The runtime composes Training endpoints, tenant context, persistence, shared messaging, an outbox store, observability, health, and a typed Document client.

Local persistence and outbox staging can share a save boundary. Document calls are separate HTTP work. Notification is downstream of messaging rather than a direct Training client. No Workflow runtime integration was found.

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/training-service/Program.cs
  • microservices/src/shared-kernel/Extensions/ObservabilityExtensions.cs
  • microservices/src/shared-kernel/Extensions/ServiceCollectionExtensions.cs
  • microservices/src/training-service/Infrastructure/Persistence.cs
  • microservices/src/shared-kernel/Messaging/OutboxProcessor.cs
  • microservices/src/training-service/Program.cs
  • microservices/src/training-service/Application/DocumentServiceClient.cs
  • microservices/src/training-service/Api/TrainingEndpoints.cs
  • microservices/src/training-service/Program.cs

See Also​

Keywords​

  • LMS operations
  • LMS Runtime Overview

Revision Information​

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