Recruitment Application Layer
Summary
Plain scoped command/query services coordinate domain objects and ports and return a lightweight Result type or DTOs.
Audience
Backend and frontend engineers, architects, QA, support, security reviewers, and operators responsible for Recruitment.
Overview
Commands perform orchestration, repository access, inline prechecks, aggregate invocation, dependency calls, audit/timeline writing, and one or more explicit saves. Queries use repository IQueryable sources and hand-written DTO projections. Result distinguishes success, validation, not-found, and conflict outcomes.
MediatR, FluentValidation, AutoMapper, pipeline behaviors, and a generic command bus are Not implemented. The folder named CQRS contains the lightweight result model, not a mediator-driven CQRS framework. Cross-cutting authorization and transaction pipelines are absent.
Requires confirmation
Production ownership, authorization policy, operational thresholds, and future design decisions require confirmation.
Source References
microservices/src/recruitment-service/Application/Commandsmicroservices/src/recruitment-service/Application/Queriesmicroservices/src/recruitment-service/Application/Commonmicroservices/src/recruitment-service/Application/Mappings.csmicroservices/src/recruitment-service/Application/Dtos.cs
Related Articles
- Recruitment technical documentation
- Recruitment business documentation
- Recruitment known limitations
See Also
Keywords
- Recruitment technical architecture
- Recruitment Service
- Application Layer
Revision Information
- Status: Draft
- Last reviewed: 2026-07-16
- Review cycle: Quarterly