Recruitment Performance Characteristics
Summary
EF indexes support common tenant/status, candidate, token, compatibility, workflow, and outbox lookups; queries remain simple and uncached.
Audience
Backend and frontend engineers, architects, QA, support, security reviewers, and operators responsible for Recruitment.
Overview
Confirmed characteristics include indexed tenant/status access, unique public-token and compatibility identities, selective detail Includes, no-tracking reads, fixed list caps, and shared HTTP-client timeouts. Some report queries materialize tenant datasets before aggregating.
No cache, distributed cache, response cache, read replica, bulk command pipeline, general pagination contract, load-test suite, Recruitment metrics, or performance budget is implemented. Public-token lookup, reporting scale, large candidate histories, export/import size, outbox backlog, and dependency latency require measurement rather than assumption.
Requires confirmation
Production ownership, authorization policy, operational thresholds, and future design decisions require confirmation.
Source References
microservices/src/recruitment-service/Infrastructure/RecruitmentDbContext.csmicroservices/src/recruitment-service/Infrastructure/Persistence.csmicroservices/src/recruitment-service/Application/Queries/RecruitmentQueries.csmicroservices/src/recruitment-service/Program.cs
Related Articles
- Recruitment technical documentation
- Recruitment business documentation
- Recruitment known limitations
See Also
Keywords
- Recruitment technical architecture
- Recruitment Service
- Performance
Revision Information
- Status: Draft
- Last reviewed: 2026-07-16
- Review cycle: Quarterly