LMS Application Layer

Summary

The Application folder contains tenant-context types, a shared validation exception used by the service, Document options/port/data records, and the concrete Document HTTP client. It does not contain LMS command/query handlers or orchestration services.

Endpoint delegates perform validation, EF queries/mutations, DTO projection, audit/timeline staging, external calls, outbox mapping, and SaveChanges. DTOs/mapping helpers live in the API file. The Document call precedes the local reference save, so it is not a distributed transaction.

MediatR, FluentValidation, AutoMapper, a Result abstraction, repository ports, and unit of work are not referenced. Errors are returned directly or translated by exception middleware.

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/Common.cs
• microservices/src/training-service/Application/DocumentServiceClient.cs
• microservices/src/training-service/Api/TrainingEndpoints.cs
• microservices/src/training-service/Program.cs

Related Articles

• LMS technical documentation
• LMS business documentation

See Also

• Technical limitations
• Technical source map

Keywords

• LMS technical architecture
• Source-backed implementation

Revision Information

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