Recruitment Processed Event Storage

Summary

A processed-integration-event ledger exists as a persistence foundation, but no Recruitment inbound consumer was found.

Audience

Developers, QA and support engineers, data reviewers, implementation partners, solution architects, and security reviewers.

Overview

ProcessedIntegrationEvent has a primary key and globally unique event identity plus event classification, optional tenant/correlation evidence, source, outcome, and processing time.

No global query filter is configured. The unique event identity supports idempotency if a consumer records processing. The inspected host does not register a Recruitment inbound consumer, so the store remains Foundation rather than evidence of active consumption.

Cleanup, retention, replay, failed-event policy, and tenant visibility require confirmation.

Requires confirmation

Production migration governance, rollback ownership, reconciliation, retention, privacy, performance, query optimization, concurrency, and operational ownership require confirmation.

Source References

• microservices/src/recruitment-service/Infrastructure/RecruitmentDbContext.cs
• microservices/src/recruitment-service/Program.cs

Related Articles

• Recruitment database documentation
• Data integrity and transactions

See Also

• Recruitment technical documentation
• Recruitment API documentation

Keywords

• Recruitment database
• Processed Event Storage

Revision Information

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