Skip to main content

Service Catalog

Summary

This catalog provides a compact, source-based view of the current HR Suit runtime boundaries. Status describes implementation maturity and does not certify deployment or production readiness.

Audience

  • Implementation partners
  • Developers and QA engineers
  • DevOps engineers
  • Solution architects and product owners

Reference Content

ServiceDomain categoryResponsibilityStatusInteraction modelData ownershipEvent roleCurrent documentation link
Gateway APIEdgeReverse proxy, route selection, compatibility, and ESS aggregationTransitionalHTTP proxy and aggregationNo domain dataCorrelation and forwarding onlyGateway overview
Current monolithTransitional platformActive backend for non-cut-over behaviorTransitionalHTTP APIs and selected async integrationDefault PostgreSQL schemaSelected producerModernization
Platform servicePlatformTenant metadata, platform administration, provisioning, and service monitoringImplementedHTTP, background jobs, messagingPlatform-owned persistenceProducer and consumerMulti-tenancy
Identity servicePlatformAuthentication, authorization context, tokens, and sessionsImplementedHTTP and eventsIdentity-owned schemaProducerSecurity overview
Employee serviceCore HREmployee and workforce organization dataImplementedHTTP and eventsEmployee-owned schemaProducerService landscape
Attendance serviceCore HRAttendance, shifts, policy, and approval lifecycleImplementedHTTP and eventsAttendance-owned schemaProducerService landscape
Leave serviceCore HRLeave requests, decisions, balances, and local employee profilesImplementedHTTP, service calls, and eventsLeave-owned schemaProducer and consumerService landscape
Payroll serviceCore HRPayroll processing and local cross-domain read modelsTransitionalHTTP and event consumptionPayroll-owned schemaProducer and consumer foundationData architecture
Recruitment serviceTalentRecruitment, offers, and onboarding lifecycleImplementedHTTP, service calls, and eventsRecruitment-owned schemaProducerService landscape
Performance serviceTalentReview cycles, appraisals, and ratingsImplementedHTTP, workflow calls, and eventsPerformance-owned schemaProducerService landscape
Training serviceTalentTraining domain foundationFoundationHTTP and event contractsTraining-owned schemaProducer/consumer foundationService landscape
Expense serviceHR operationsExpense claim lifecycleImplementedHTTP, service calls, and eventsExpense-owned schemaProducerService landscape
Asset serviceHR operationsAsset and assignment lifecycleImplementedHTTP, service calls, and eventsAsset-owned schemaProducerService landscape
Helpdesk serviceHR operationsHR support ticket foundationFoundationHTTP and event contractsHelpdesk-owned schemaProducer foundationService landscape
Workflow serviceShared capabilityDefinitions, instances, tasks, and approvalsImplementedHTTP and eventsWorkflow-owned schemaProducerService landscape
Document serviceShared capabilityDocument metadata, processing, storage abstraction, and projectionsTransitionalHTTP, provider calls, and eventsDocument-owned schema and configured storageProducer and consumerData architecture
Notification serviceShared capabilityNotification template and dispatch foundationFoundationEvent consumption and provider callsNotification-owned schemaConsumerMessaging
Integration serviceIntegrationEvent routing, audit, retry, and dead-letter handlingFoundationEvent consumption and outbound HTTPIntegration operational schemaConsumer/routerMessaging
Reporting serviceReportingFuture standalone reporting boundarySkeletonNo confirmed runtime interactionNo confirmed ownershipNone confirmedService landscape
HR operations serviceTransitional/skeletonFuture boundary requiring responsibility confirmationSkeletonNo confirmed runtime interactionNo confirmed ownershipNone confirmedService landscape
Tenant provisioning serviceTransitional/skeletonFuture standalone provisioning boundarySkeletonNo confirmed runtime interactionNo confirmed ownershipNone confirmedService landscape

The organization capability is represented within current employee/monolith boundaries rather than listed as a separate executable service. The standalone tenant provisioning skeleton is distinct from provisioning behavior implemented in the platform service.

See Also

Keywords

  • Runtime inventory
  • Service ownership
  • Event role

Revision Information

  • Last reviewed: 2026-07-14
  • Owner: architecture-team
  • Status: Draft