Skip to main content

Indexes and Constraints

Audience​

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

Reference Content​

Summary​

Indexes primarily support tenant-scoped lookup, status queues, business-code uniqueness, parent-child navigation and event idempotency.

Confirmed patterns​

  • Tenant plus lifecycle status for Candidate, Onboarding, Employee and other queue/list views.
  • Tenant plus email or organization reference for common employee/candidate access.
  • Unique compatibility identifiers on selected Recruitment aggregates.
  • Unique tenant/employee-code constraint in Employee Service.
  • Unique tenant/code constraints for Employee departments and designations.
  • Parent-reference support indexes on Offer and Candidate child collections.
  • Unique event identifiers in contexts with processed-event/outbox idempotency constraints.
  • Status/time indexes for outbox polling.

Access-path model​

Limits​

The source inventory does not establish production selectivity, index usage, query plans or contention. No performance benchmark should be inferred. Compatibility initializer-created optional indexes are intentionally described only as a mechanism, not by physical name or SQL.

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.cs
  • microservices/src/employee-service/Infrastructure/EmployeeDbContext.cs
  • Data/AppDbContext.cs

See Also​

Keywords​

  • Onboarding database
  • Offboarding database
  • Lifecycle persistence

Revision Information​

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