Recruitment Employee Integration

Summary

Onboarding completion synchronously calls Employee Service through a typed HTTP client and retry-oriented provisioning gateway.

Audience

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

Overview

Provisioning uses a deterministic employee code so a retry can resolve an existing Employee rather than duplicate it. Employee login creation is not supported, and reporting-manager identifiers cannot be mapped to Employee Service identifiers. No distributed transaction spans Employee and Recruitment; reconciliation ownership requires confirmation.

Requires confirmation

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

Source References

• microservices/src/recruitment-service/Application/Commands/OnboardingCommands.cs
• microservices/src/recruitment-service/Application/Common/Gateways.cs
• microservices/src/recruitment-service/Infrastructure/EmployeeServiceClient.cs
• microservices/src/recruitment-service/Infrastructure/Gateways.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
• Employee Integration

Revision Information

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