Skip to main content

LMS Service Architecture

Summary​

Training Service owns LMS HTTP behavior and PostgreSQL-backed training state. It uses ASP.NET Core 8 minimal APIs, EF Core 8, a shared kernel, and shared contracts.

The bounded context owns courses, learning paths, enrollments, completions, assessments, certificates, sessions, trainers, materials, audit/timeline, processed-event storage, and outbox rows. Layering is folder/namespace convention inside one deployable project, not separate assemblies. Current maturity is Transitional.

Requires confirmation​

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

Source References​

  • microservices/src/training-service/training-service.csproj
  • microservices/src/training-service/Program.cs
  • microservices/src/training-service/Api/TrainingEndpoints.cs
  • microservices/src/training-service/Infrastructure/TrainingDbContext.cs
  • microservices/src/training-service/Application/DocumentServiceClient.cs
  • microservices/src/contracts/Events/TrainingLifecycleEvents.cs

See Also​

Keywords​

  • LMS technical architecture
  • Source-backed implementation

Revision Information​

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