Recruitment Project Structure
Summary
A single web project is organized into API, Application, Domain, Infrastructure, Messaging, migration, and host-composition areas.
Audience
Backend and frontend engineers, architects, QA, support, security reviewers, and operators responsible for Recruitment.
Overview
| Area | Confirmed contents |
|---|---|
| API | Native, public, compatibility, result-mapping, and policy definitions |
| Application | Commands, queries, DTOs, mappings, workflow contracts, compatibility translation, and ports |
| Domain | Aggregates, child entities, repositories, enums, value objects, primitives, and domain events |
| Infrastructure | EF Core context/repositories, HTTP clients/gateways, writers, migrations, and development seeding |
| Messaging | Hosted outbox relay |
| Host composition | Dependency injection, authentication, health, middleware, migrations, and route mapping |
No separate Domain/Application/Infrastructure project files exist, so dependency direction is not compiler-enforced. Generated migration files are persistence evidence, not business policy.
Requires confirmation
Production ownership, authorization policy, operational thresholds, and future design decisions require confirmation.
Source References
microservices/src/recruitment-service/recruitment-service.csprojmicroservices/src/recruitment-service/Program.csmicroservices/src/recruitment-service/Apimicroservices/src/recruitment-service/Applicationmicroservices/src/recruitment-service/Domainmicroservices/src/recruitment-service/Infrastructuremicroservices/src/recruitment-service/Messaging
Related Articles
- Recruitment technical documentation
- Recruitment business documentation
- Recruitment known limitations
See Also
Keywords
- Recruitment technical architecture
- Recruitment Service
- Project Structure
Revision Information
- Status: Draft
- Last reviewed: 2026-07-16
- Review cycle: Quarterly