Skip to main content

Runtime Composition and Project Structure

Summary​

The extracted runtime is a layered .NET service with PostgreSQL persistence, shared telemetry, external service clients, message relay, and tenant context. The client portal supplies the Recruitment Onboarding and HR Operations user surfaces.

Audience​

Developers, QA, support, release engineers, and solution architects.

Runtime composition​

Recruitment Service is one .NET web project targeting the verified framework version and referencing shared-kernel and contracts projects. Startup registers tenant context, persistence, repositories, audit/timeline writers, typed Document and Employee clients, optional requisition Workflow client, command/query services, compatibility adapters, JWT processing, health, endpoint discovery, and an outbox background relay.

Development-only migration and seeding behavior exists; production migration ownership remains out of process. Runtime configuration values and infrastructure addresses are intentionally excluded here.

Solution structure​

LocationResponsibility
ApiNative/public/compatibility endpoint mapping, policies, result translation
ApplicationDTOs, commands, queries, mappings, ports, compatibility adapters, requisition Workflow abstraction
DomainAggregates, entities, enums, value objects, domain events, repository ports
InfrastructureEF Core context/repositories/unit of work, tenant context, typed clients, gateways, migrations
MessagingHosted outbox relay
Monolith Controllers and ModelsCompatibility onboarding, exit, generic task, notification dispatch
Client portal HR pagesProtected onboarding and exit routes, form state, validation, API client calls

Frontend composition​

The React router maps protected Recruitment onboarding and HR Operations exit pages. Navigation visibility combines module/feature metadata, permission labels, and role/audience labels. Frontend protection is not a substitute for backend authorization.

Requires confirmation​

  • Production dependency topology and readiness requirements.
  • Whether development-time migrations and seed behavior are disabled in every production deployment.
  • Final frontend ownership when compatibility routing is retired.

Source References​

  • microservices/src/recruitment-service/Program.cs
  • microservices/src/recruitment-service/recruitment-service.csproj
  • microservices/src/recruitment-service/Api
  • microservices/src/recruitment-service/Application
  • microservices/src/recruitment-service/Domain
  • microservices/src/recruitment-service/Infrastructure
  • microservices/src/recruitment-service/Messaging/OutboxRelayHostedService.cs
  • Controllers/HrOperationsController.cs
  • UI/salary-ui/apps/client-hrms-portal/src/App.tsx
  • UI/salary-ui/apps/client-hrms-portal/src/components/AppLayout.tsx

See Also​

Keywords​

  • Runtime composition
  • Project structure
  • Client portal

Revision Information​

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