Recruitment Infrastructure Layer

Summary

Infrastructure implements EF repositories and unit of work, tenant and evidence writers, HTTP clients/gateways, migrations/seeding, and outbox storage.

Audience

Backend and frontend engineers, architects, QA, support, security reviewers, and operators responsible for Recruitment.

Overview

Infrastructure adapters include RecruitmentDbContext, repositories, UnitOfWork, audit/timeline writers, tenant resolution, Document/Employee/Workflow clients and gateways, migration support, development seeding, and the shared outbox store. Messaging adds a hosted relay around the shared processor.

Public lookup paths deliberately bypass global query filters and recover tenant from an opening or opaque token. Development-only fallbacks exist in dependency gateways; they are not production architecture and exact controls are intentionally excluded.

Requires confirmation

Production ownership, authorization policy, operational thresholds, and future design decisions require confirmation.

Source References

• microservices/src/recruitment-service/Infrastructure
• microservices/src/recruitment-service/Messaging/OutboxRelayHostedService.cs
• microservices/src/recruitment-service/Program.cs

Related Articles

• Recruitment technical documentation
• Recruitment business documentation
• Recruitment known limitations

See Also

• Recruitment module
• Recruitment API foundation

Keywords

• Recruitment technical architecture
• Recruitment Service
• Infrastructure Layer

Revision Information

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