LMS Gateway and HTTP Boundaries

Summary

Source-backed distinction between event consumption and synchronous HTTP integration.

Audience

Engineering, integration, QA, architecture, security, product, and service owners.

Reference Content

Gateway forwards an employee-self-service training read and includes training data in its dashboard aggregation. It is not a Training event consumer. Its retry/timeout behavior applies to HTTP requests, not event delivery.

Training uses a typed HTTP client for material and certificate document operations. Document Service is not a confirmed Training event consumer. External success and local persistence are not distributed-transactional.

Employee references are accepted/stored as identifiers; no Training-to-Employee HTTP client or Training-event subscription was found. No Training Workflow integration was found. These absences must not be described as subscriptions.

Source References

• microservices/src/gateway-api/EssEndpoints.cs
• microservices/src/training-service/Application/DocumentServiceClient.cs
• microservices/src/training-service/Api/TrainingEndpoints.cs

Related Articles

• LMS Events documentation
• LMS technical documentation

See Also

• Verified event catalog
• Event limitations

Keywords

• LMS events
• Training contracts
• Source-backed integration

Revision Information

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