Recruitment Commands and Queries

Summary

Minimal API handlers invoke scoped command/query services directly; commands return Result values and queries return hand-mapped DTOs and report aggregates.

Audience

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

Overview

Command flow

Query flow

There is no mediator or separate command/query database. Some report methods materialize tenant datasets before aggregation; list queries use fixed caps rather than a general pagination contract.

Requires confirmation

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

Source References

• microservices/src/recruitment-service/Application/Commands
• microservices/src/recruitment-service/Application/Queries/RecruitmentQueries.cs
• microservices/src/recruitment-service/Api/RecruitmentEndpoints.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
• Commands and Queries

Revision Information

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