Skip to main content

LMS Event Limitations

Summary

The event model is transitional: contract staging exists, while domain-event, relay, governance, and several lifecycle capabilities are absent.

Audience

Engineering, integration, QA, architecture, security, product, and support reviewers.

Reference Content

AreaVerified limitationClassification
Domain modelNo Training domain-event abstraction, collection, or domain-event types; contracts are created directly.Transitional
PublicationOutbox messages and processor registration exist, but no active Training relay trigger was found.Transitional
Inbound integrationTraining has no confirmed inbound event contracts or consumers.Not implemented
Certificate expiryCertificateExpiringSoonEvent is defined and recognized but has no Training invocation.Not implemented
RecoveryNo active replay, outbox cleanup, reconciliation flow, or terminal publisher retry limit was found.Not implemented / Requires confirmation
Dead-letteringNo active dead-letter wiring was found for the confirmed Notification consumer.Not implemented
OrderingNo aggregate, employee, tenant, global, or broker ordering guarantee is implemented.Foundation
CorrelationTraining producers leave correlation and causation context unset.Foundation
Version governanceNo compatibility validation, deprecation policy, or multi-version migration strategy was found.Requires confirmation
Course lifecycleNo verified course create, update, publish, archive, material, module, or lesson event contracts.Not implemented
Session lifecycleNo session completion, cancellation, attendance, capacity, or participant events.Not implemented
Certificate lifecycleNo produced expiry, revocation, renewal, or document-compensation events.Not implemented
Other learning lifecycleNo learning-path event family was verified.Not implemented
TestingExisting smoke evidence does not prove relay or broker delivery; dedicated event suites were not found.Foundation

Publication ownership, reconciliation ownership, retention, contract governance, and operational failure ownership Require confirmation.

Source References

  • microservices/src/contracts/Events/TrainingLifecycleEvents.cs
  • microservices/src/training-service/Api/TrainingEndpoints.cs
  • microservices/src/training-service/Infrastructure/TrainingDbContext.cs
  • microservices/src/training-service/Infrastructure/Persistence.cs
  • microservices/src/training-service/Program.cs
  • microservices/src/notification-service/Messaging/NotificationEventConsumer.cs

See Also

Keywords

  • Integration limitations
  • Event maturity
  • Requires confirmation

Revision Information

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