Recruitment Gateway Integration

Summary

Gateway routing can keep the existing Recruitment compatibility surface on the monolith or route it to Recruitment Service while a shadow service path remains available for verification.

Audience

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

Overview

Compatibility commands translate numeric identities and monolith-shaped contracts into native services; they do not intentionally duplicate business logic. Gateway cutover changes route ownership, not data ownership or reconciliation. A Recruitment smoke helper verifies shadow/toggle behavior, but no standalone parity comparator, go/no-go helper, cutover runbook, or backfill implementation was found.

Requires confirmation

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

Source References

• microservices/src/gateway-api/Program.cs
• microservices/src/recruitment-service/Api/RecruitmentCompatEndpoints.cs
• microservices/src/recruitment-service/Application/Compatibility
• UI/salary-ui/apps/client-hrms-portal/src/utils/ProtectedRoute.tsx

Related Articles

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

See Also

• Recruitment module
• Recruitment API foundation

Keywords

• Recruitment technical architecture
• Recruitment Service
• Gateway Integration

Revision Information

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