Recruitment API Compatibility and Routing

Summary

Gateway configuration selects the monolith or Recruitment Service for compatibility routes and retains a shadow service path.

Audience

Developers, QA and support engineers, implementation partners, architects, and security reviewers working with Recruitment APIs.

Overview

Compatibility routes retain numeric identifiers and monolith-shaped records while translating into native command/query services. Native routes use Recruitment-owned identifiers and DTOs.

The routing toggle changes request ownership; it does not prove data parity. Candidate resume routing receives a narrower service override, while unrelated document/import-export routes remain with their existing owners. Rollback is route-toggle based, but data reconciliation and compatibility retirement remain Requires confirmation.

Requires confirmation

Production exposure, authorization policy, ownership, compatibility parity, operational limits, and version governance require confirmation.

Source References

• microservices/src/recruitment-service/Api/RecruitmentCompatEndpoints.cs
• microservices/src/recruitment-service/Application/Compatibility/CompatCommands.cs
• microservices/src/recruitment-service/Application/Compatibility/CompatQueries.cs
• microservices/src/gateway-api/Program.cs

Related Articles

• Recruitment API documentation
• Recruitment technical documentation

See Also

• Recruitment module
• Recruitment business documentation

Keywords

• Recruitment API
• Compatibility and Routing

Revision Information

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