Recruitment Job Opening Storage

Summary

Job-opening persistence stores position lifecycle and organizational references as an independent aggregate.

Audience

Developers, QA and support engineers, data reviewers, implementation partners, solution architects, and security reviewers.

Overview

Job Opening has a primary key, unique compatibility identity, tenant/status index, bounded descriptive fields, string-converted status, and timestamps.

Requisition, organizational, and manager identifiers are logical references; no EF foreign key is configured for them. Public repository queries deliberately bypass global filters and apply source-defined open-status and optional tenant predicates.

There is no opening delete/archive persistence path or tenant-scoped uniqueness constraint for titles.

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.cs
• microservices/src/recruitment-service/Domain/Recruitment/JobOpening.cs
• microservices/src/recruitment-service/Infrastructure/Persistence.cs

Related Articles

• Recruitment database documentation
• Data integrity and transactions

See Also

• Recruitment technical documentation
• Recruitment API documentation

Keywords

• Recruitment database
• Job Opening Storage

Revision Information

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