LMS Read Operations

Summary

Audience

Developers, QA, architecture, support, and reporting reviewers.

Reference Content

No query classes/handlers exist. Endpoint-local reads cover health data; course, material, path, enrollment/detail, assessment, certificate, and session lists; material/certificate download; CSV templates/exports; dashboard/course/enrollment/assessment/certificate/path/manager reports; audit; timeline; and outbox.

List ordering is explicitly confirmed only on selected reads; most have no filters, pagination, or bounded result size. Reporting is live EF aggregation, not a separate analytics architecture. AsNoTracking is used on several reads, not uniformly. Employee ESS forwards the enrollment list rather than a dedicated self-filtered Training query, so ownership/scoping requires confirmation.

Requires confirmation

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

Source References

• microservices/src/training-service/Api/TrainingEndpoints.cs
• microservices/src/training-service/Infrastructure/TrainingDbContext.cs
• microservices/src/gateway-api/EssEndpoints.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