Recruitment Domain Model

Summary

Six aggregate roots and their child entities model hiring state. Structural value objects validate names, contacts, monetary concepts, compensation structure, and public tokens.

Audience

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

Overview

Aggregate identity uses stable GUIDs; compatibility identities are separate numeric values. Domain events queue on aggregate roots. CandidateName and CompensationBreakup are EF-owned value objects; email, phone, money, and public tokens are domain validation helpers. No domain-service class was found: coordination is implemented in application command services.

Requires confirmation

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

Source References

• microservices/src/recruitment-service/Domain/Common/DomainPrimitives.cs
• microservices/src/recruitment-service/Domain/Common/ValueObjects.cs
• microservices/src/recruitment-service/Domain/Common/Enums.cs
• microservices/src/recruitment-service/Domain/Recruitment

Related Articles

• Recruitment technical documentation
• Recruitment business documentation
• Recruitment known limitations

See Also

• Recruitment module
• Recruitment API foundation

Keywords

• Recruitment technical architecture
• Recruitment Service
• Domain Model

Revision Information

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