Entity Mappings
Audience
Developers, QA and support engineers, data reviewers, implementation partners, solution architects, privacy reviewers and security reviewers.
Reference Content
Summary
Lifecycle mappings combine aggregate roots, configured children, owned values, logical cross-aggregate references and operational ledgers.
Mapping categories
| Category | Examples | Database behavior |
|---|---|---|
| Aggregate root | Candidate, Offer, Onboarding, Employee, Asset, ExitRequest | Independent key and lifecycle |
| Configured child | Candidate stage history, Offer letter/revision/approval, Employee details, Asset assignment history | Parent relationship; configured cascades where confirmed |
| Owned value | Candidate name, Offer compensation, Employee employment | Stored as part of owner lifecycle |
| Logical reference | Onboarding to candidate/offer/employee, Employee to organization/manager | Identifier without configured EF navigation relationship |
| Projection | Payroll/Leave/Attendance employee profile | Consumer-owned local state |
| Operational ledger | Outbox, processed event, delivery attempt | Delivery/idempotency evidence |
Aggregate view
Design implication
Logical references preserve service boundaries but move existence and staleness validation to application/integration code. Owned values cannot be independently versioned or retained without their owner. Operational ledgers must not be treated as domain aggregates.
Requires confirmation
Unless explicitly confirmed above, production migration governance, rollback, reconciliation, retention, privacy, performance, concurrency and operational ownership require confirmation.
Source References
microservices/src/recruitment-service/Infrastructure/RecruitmentDbContext.csmicroservices/src/employee-service/Infrastructure/EmployeeDbContext.csData/AppDbContext.cs
Related Articles
See Also
Keywords
- Onboarding database
- Offboarding database
- Lifecycle persistence
Revision Information
- Status: Draft
- Last reviewed: 2026-07-20
- Review cycle: Quarterly