Recruitment Database Overview

Summary

A single EF Core model persists Recruitment aggregates, child records, operational evidence, inbound idempotency, and outbound event intent.

Audience

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

Overview

The context configures object mapping directly in OnModelCreating; no separate IEntityTypeConfiguration classes were found. Candidate name and offer compensation are owned values stored with their owners. Compatibility adapters use the same model rather than a second compatibility store.

The provider is configured through the service host. Physical database and schema identifiers are intentionally excluded.

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/Infrastructure/Persistence.cs
• microservices/src/recruitment-service/Infrastructure/Migrations/RecruitmentDbContextModelSnapshot.cs

Related Articles

• Recruitment database documentation
• Recruitment technical documentation

See Also

• Recruitment API documentation
• Recruitment module

Keywords

• Recruitment database
• Database Overview

Revision Information

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