LMS Technical Documentation

Summary

Training Service is a single ASP.NET Core minimal-API process targeting .NET 8. API, Application, Domain, and Infrastructure folders share one project; endpoint delegates orchestrate EF Core, document calls, evidence, and outbox staging directly.

Audience

Engineering, QA, support, operations, architecture, security, and implementation teams.

Overview

The implementation is Transitional: tenant-scoped persistence and broad LMS capabilities exist, but conventional command/query, repository/unit-of-work, domain-event, service-local authorization, background outbox relay, compatibility, caching, and dedicated automated-test layers are absent.

Documentation map

• Architecture, runtime, structure, and layers
• Domain, course, enrollment, path, session, assessment, and certificate
• Application, commands, queries, validation, repositories, and persistence
• Messaging, integrations, security, observability, transition, testing, limitations, and source map

Requires confirmation

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

Source References

• microservices/src/training-service/Program.cs
• microservices/src/training-service/training-service.csproj
• microservices/src/training-service/Api/TrainingEndpoints.cs
• microservices/src/training-service/Domain/TrainingEntities.cs
• microservices/src/training-service/Infrastructure/TrainingDbContext.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