Recruitment Database Ownership and Boundaries
Summary
Recruitment owns lifecycle state and persistence evidence while retaining logical references to external Workflow, Employee, and Document records.
Audience
Developers, QA and support engineers, data reviewers, implementation partners, solution architects, and security reviewers.
Overview
Recruitment owns requisitions, openings, candidates and children, interviews and feedback, offers and children, onboarding, audit/timeline evidence, processed-event markers, and outbox messages.
Document content remains outside Recruitment; only document references and integrity metadata are persisted. Employee and Workflow identifiers are logical external references. No EF relationship connects Recruitment objects to external services.
There is no separate reporting, compatibility, backfill, or read-model DbContext. Operational ownership, reconciliation, retention, and archival require confirmation.
Requires confirmation
Production migration governance, rollback ownership, reconciliation, retention, privacy, performance, query optimization, concurrency, and operational ownership require confirmation.
Source References
microservices/src/recruitment-service/Infrastructure/RecruitmentDbContext.csmicroservices/src/recruitment-service/Domain/Recruitmentmicroservices/src/recruitment-service/Infrastructure/DocumentServiceClient.csmicroservices/src/recruitment-service/Infrastructure/EmployeeServiceClient.cs
Related Articles
See Also
Keywords
- Recruitment database
- Ownership and Boundaries
Revision Information
- Status: Draft
- Last reviewed: 2026-07-16
- Review cycle: Quarterly