Skip to main content

LMS Compatibility and Transition

Summary​

No Training compatibility endpoints, legacy adapter, monolith projection, shadow read/write path, backfill runner, parity script, cutover helper, rollback helper, or transitional database context was found.

The service and UI use “Training” and “LMS” labels for the same canonical bounded context; this naming coexistence is not a compatibility implementation. CSV import/export is a canonical bulk feature, not a legacy adapter. Gateway ESS is composition, not shadow routing.

Compatibility-specific model/event differences and retirement plans are therefore Not implemented/not applicable in the current source. Naming governance and any external legacy consumers require 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/Program.cs
  • microservices/src/training-service/Api/TrainingEndpoints.cs
  • microservices/src/gateway-api/EssEndpoints.cs
  • UI/salary-ui/apps/client-hrms-portal/src/pages/hr/TalentAdminPages.tsx

See Also​

Keywords​

  • LMS technical architecture
  • Source-backed implementation

Revision Information​

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