Skip to main content

LMS Document Integration

Summary​

IDocumentServiceClient defines store/download operations; DocumentServiceClient is the typed HTTP adapter. Course-material upload sends binary/metadata to Document Service then stores a local TrainingMaterial reference. Certificate generation stores generated content externally then saves the reference; downloads retrieve by reference.

Training owns LMS metadata and the reference; Document Service owns the binary record. Local material-reference deletion does not delete the external binary. Empty content, missing configuration, transport failure, rejected response, missing document, timeout, and empty response map to source-defined errors.

There is no distributed transaction, compensating cleanup, versioning, retention, malware scanning evidence, external deletion, or reference-reconciliation process confirmed. Document metadata/content values are intentionally excluded.

Requires confirmation​

Fine-grained authorization, production ownership, operational governance, and future architectural boundaries require confirmation where not implemented.

Source References​

  • microservices/src/training-service/Application/DocumentServiceClient.cs
  • microservices/src/training-service/Program.cs
  • microservices/src/training-service/Api/TrainingEndpoints.cs
  • microservices/src/training-service/Domain/TrainingEntities.cs

See Also​

Keywords​

  • LMS technical architecture
  • Source-backed implementation

Revision Information​

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