Recruitment Indexing and Query Patterns
Summary
The snapshot contains 35 secondary indexes supporting compatibility identities, tokens, tenant/status access, relationships, Workflow lookup, audit chronology, and outbox processing.
Audience
Developers, QA and support engineers, data reviewers, implementation partners, solution architects, and security reviewers.
Overview
Verified counts
| Index classification | Count |
|---|---|
| Unique | 10 |
| Non-unique | 25 |
| Snapshot total | 35 |
| Explicitly declared in model code | 31 |
| Convention relationship-support indexes | 4 |
Unique indexes cover six compatibility identifiers, two public tokens, processed-event identity, and outbox event identity.
Non-unique indexes support tenant/status, tenant/candidate, tenant/opening, child-parent lookup, Workflow instance lookup, document type, offer revision/decision chronology, audit/timeline chronology, and outbox status/time scanning.
Repository queries use no-tracking reads, selected Includes, fixed caps, tenant filters, token lookups, and compatibility lookups. There is no caching, read replica, query-hint layer, or performance benchmark. Query optimization and deployed index monitoring 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/Infrastructure/Migrations/RecruitmentDbContextModelSnapshot.csmicroservices/src/recruitment-service/Infrastructure/Persistence.csmicroservices/src/recruitment-service/Application/Queries/RecruitmentQueries.cs
Related Articles
See Also
Keywords
- Recruitment database
- Indexing and Query Patterns
Revision Information
- Status: Draft
- Last reviewed: 2026-07-16
- Review cycle: Quarterly