LMS Processed Event Storage

Summary

Source-backed ProcessedIntegrationEvent persistence and current usage boundary.

Audience

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

Reference Content

ProcessedIntegrationEvent stores its own identifier, unique external event identity, event type, optional tenant/correlation metadata, source service, outcome, and processing time. Event identity uniqueness is the only confirmed duplicate-detection constraint.

No Training runtime code was found that inserts or queries this set outside DbContext exposure and migration metadata. It therefore represents Foundation storage for inbound idempotency rather than a verified active consumer workflow.

The object has no global tenant query filter, tenant index, cleanup job, retention policy, outcome-specific index, or mapped API. The optional tenant property does not by itself enforce isolation. Payload content is not stored on this object.

Source References

• microservices/src/training-service/Domain/TrainingEntities.cs
• microservices/src/training-service/Infrastructure/TrainingDbContext.cs
• microservices/src/training-service/Infrastructure/Migrations/TrainingDbContextModelSnapshot.cs
• microservices/src/training-service/Program.cs

Related Articles

• LMS database documentation
• LMS technical documentation

See Also

• Schema reference
• Database testing guide

Keywords

• LMS database
• Training persistence
• Source-backed model

Revision Information

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