LMS Event Architecture
Summary
Source-backed architecture of lifecycle mutations, outbox staging, shared messaging, and consumption.
Audience
Engineering, integration, QA, architecture, security, and support reviewers.
Reference Content
Training endpoints directly mutate entities and invoke static infrastructure helpers. Helpers construct contracts, validate required categories, and add serialized outbox records. One DbContext SaveChanges normally commits the entity, evidence, and outbox intent locally.
Shared messaging registration provides a transport abstraction, publisher, and scoped outbox processor. Training Program does not register a hosted relay or call the processor. Notification independently hosts a consumer for recognized event names.
There is no domain-event-to-integration-event pipeline, inbound Training handler, Workflow event integration, or event-based Gateway/Document boundary.
Source References
microservices/src/training-service/Api/TrainingEndpoints.csmicroservices/src/training-service/Infrastructure/TrainingDbContext.csmicroservices/src/training-service/Program.csmicroservices/src/shared-kernel/Extensions/MessagingExtensions.csmicroservices/src/notification-service/Program.cs
Related Articles
See Also
Keywords
- LMS events
- Training contracts
- Source-backed integration
Revision Information
- Status: Draft
- Last reviewed: 2026-07-17
- Review cycle: Quarterly