Recruitment Layered Architecture
Summary
Domain behavior is invoked by application services through repository and gateway ports; infrastructure implements those ports; minimal APIs and compatibility adapters are entry points.
Audience
Backend and frontend engineers, architects, QA, support, security reviewers, and operators responsible for Recruitment.
Overview
Aggregate methods own local invariants and state changes. Application services coordinate multiple aggregates, dependencies, audit/timeline records, and save boundaries. Infrastructure owns persistence, HTTP, messaging, and tenant-context adapters. Because all folders compile into one assembly, unwanted dependencies are possible even though the current organization expresses this layering.
Requires confirmation
Production ownership, authorization policy, operational thresholds, and future design decisions require confirmation.
Source References
microservices/src/recruitment-service/Domainmicroservices/src/recruitment-service/Applicationmicroservices/src/recruitment-service/Infrastructuremicroservices/src/recruitment-service/Apimicroservices/src/recruitment-service/Program.cs
Related Articles
- Recruitment technical documentation
- Recruitment business documentation
- Recruitment known limitations
See Also
Keywords
- Recruitment technical architecture
- Recruitment Service
- Layering
Revision Information
- Status: Draft
- Last reviewed: 2026-07-16
- Review cycle: Quarterly