Recruitment Dependency Injection

Summary

The ASP.NET Core container composes scoped persistence/application services, typed HTTP clients, shared messaging, authentication, health, and the hosted relay.

Audience

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

Overview

Scoped registrations cover DbContext, tenant context, unit of work, repositories, writers, command/query services, compatibility services, gateways, and outbox store/processor. Typed HTTP clients provide Workflow, Employee, and Document transport. Shared event-bus components are singleton or scoped according to their role. The outbox relay is a hosted service.

Workflow registration selects a real or null client based on configuration. No external container, module scanner, mediator registration, validation pipeline, decorator chain, or explicit transaction behavior is used.

Requires confirmation

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

Source References

• microservices/src/recruitment-service/Program.cs
• microservices/src/shared-kernel/Extensions/MessagingExtensions.cs
• microservices/src/shared-kernel/Extensions/ObservabilityExtensions.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
• Dependency Injection

Revision Information

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