Service Landscape
Summary
The current HR Suit landscape contains an active monolith, an edge gateway, extracted domain services, shared capability services, and three standalone skeleton services.
Audience
- Developers and QA engineers
- DevOps engineers
- Implementation partners
- Solution architects and product owners
Reference Content
Maturity describes source implementation, not deployment or production certification. Implemented means substantial executable behavior is present; Transitional means coexistence or migration is active; Foundation means a usable but incomplete boundary exists; Skeleton means only a future service boundary is established.
Edge and gateway
| Service | Responsibility | Maturity | Interaction style | Data ownership | Main dependencies | Documentation status |
|---|---|---|---|---|---|---|
| Gateway API | Reverse proxy, configuration-controlled route selection, compatibility forwarding, and ESS aggregation. | Transitional | Synchronous HTTP aggregation and proxying | No domain database | Portals, monolith, selected services | Foundation overview |
| Current monolith | Active backend for routes and business behavior not fully cut over. | Transitional | Synchronous APIs and selected event publication | Default PostgreSQL schema | Gateway, PostgreSQL, messaging and providers | Foundation overview |
Platform and identity
| Service | Responsibility | Maturity | Interaction style | Data ownership | Main dependencies | Documentation status |
|---|---|---|---|---|---|---|
| Platform service | Platform tenant metadata, administration, commercial/configuration foundations, provisioning, and service monitoring. | Implemented | HTTP APIs, background work, event producer/consumer | Platform-owned schemas and optional provisioned tenant database | PostgreSQL, RabbitMQ, registered services | Foundation overview |
| Identity service | Authentication, tokens, roles, permissions, sessions, and security events. | Implemented | Authenticated HTTP APIs and events | Identity-owned schema | PostgreSQL, token consumers, messaging | Foundation overview |
Core HR
| Service | Responsibility | Maturity | Interaction style | Data ownership | Main dependencies | Documentation status |
|---|---|---|---|---|---|---|
| Employee service | Employee records, employment lifecycle, and organization-related workforce data. | Implemented | HTTP APIs and events | Employee-owned schema | PostgreSQL, messaging | Foundation overview |
| Attendance service | Attendance capture, submission/approval lifecycle, shifts, and policy foundations. | Implemented | HTTP APIs and events | Attendance-owned schema | PostgreSQL, payroll guard, messaging | Foundation overview |
| Leave service | Leave requests, decisions, balances, and employee profile synchronization. | Implemented | HTTP APIs, typed service calls, and events | Leave-owned schema and local profile projection | Employee events, attendance, workflow, PostgreSQL | Foundation overview |
| Payroll service | Payroll calculation and lifecycle processing using local workforce and HR read models. | Transitional | HTTP APIs and event-driven read models | Payroll-owned schema | Employee, attendance, leave and expense events; PostgreSQL | Foundation overview |
Talent
| Service | Responsibility | Maturity | Interaction style | Data ownership | Main dependencies | Documentation status |
|---|---|---|---|---|---|---|
| Recruitment service | Requisitions, candidates, interviews, offers, onboarding, and related lifecycle processing. | Implemented | HTTP APIs, typed service calls, and events | Recruitment-owned schema | Workflow, documents, employee service, PostgreSQL | Foundation overview |
| Performance service | Review cycles, goals, appraisals, ratings, and approval integration. | Implemented | HTTP APIs, workflow calls, and events | Performance-owned schema | Workflow, PostgreSQL, messaging | Foundation overview |
| Training service | Training catalog, assignment, enrollment, and completion foundations. | Foundation | HTTP APIs and event contracts | Training-owned schema | PostgreSQL and messaging contracts | Foundation overview |
HR operations
| Service | Responsibility | Maturity | Interaction style | Data ownership | Main dependencies | Documentation status |
|---|---|---|---|---|---|---|
| Expense service | Expense claims, receipts, decisions, payment state, and approval integration. | Implemented | HTTP APIs, typed service calls, and events | Expense-owned schema | Documents, workflow, payroll guard, PostgreSQL | Foundation overview |
| Asset service | Asset lifecycle, assignments, returns, condition, and related approvals/documents. | Implemented | HTTP APIs, typed service calls, and events | Asset-owned schema | Documents, workflow, PostgreSQL | Foundation overview |
| Helpdesk service | HR support ticket and related operational foundations. | Foundation | HTTP APIs and event contracts | Helpdesk-owned schema | PostgreSQL and messaging contracts | Foundation overview |
| Workflow service | Reusable workflow definitions, instances, tasks, actions, and lifecycle events. | Implemented | HTTP APIs and events | Workflow-owned schema | Calling domain services, PostgreSQL, messaging | Foundation overview |
Shared capabilities
| Service | Responsibility | Maturity | Interaction style | Data ownership | Main dependencies | Documentation status |
|---|---|---|---|---|---|---|
| Document service | Document metadata, generation/upload flows, provider abstraction, and local projections. | Transitional | HTTP APIs, storage provider calls, and events | Document-owned schema plus configured object storage | Storage provider, PostgreSQL, messaging | Foundation overview |
| Notification service | Notification templates and in-application/email dispatch foundations. | Foundation | Event consumption and provider dispatch | Notification-owned schema | RabbitMQ, email provider, PostgreSQL | Foundation overview |
Integration and reporting
| Service | Responsibility | Maturity | Interaction style | Data ownership | Main dependencies | Documentation status |
|---|---|---|---|---|---|---|
| Integration service | Integration-event routing, audit, retries, and dead-letter handling. | Foundation | Event consumer and configured outbound HTTP | Integration-owned operational schema | RabbitMQ, configured downstream systems, PostgreSQL | Foundation overview |
| Reporting service | Future standalone reporting boundary. | Skeleton | No confirmed business interaction | No confirmed database ownership | Requires future design | Placeholder only |
Transitional or skeleton services
| Service | Responsibility | Maturity | Interaction style | Data ownership | Main dependencies | Documentation status |
|---|---|---|---|---|---|---|
| HR operations service | Future consolidated or coordinating HR operations boundary; final responsibility requires confirmation. | Skeleton | No confirmed business interaction | No confirmed database ownership | Requires future design | Placeholder only |
| Tenant provisioning service | Future standalone provisioning boundary. Current provisioning capability is owned by the platform service. | Skeleton | No confirmed business interaction | No confirmed database ownership | Platform design requires confirmation | Placeholder only |
Interpretation
Service boundaries are at different migration stages. “Implemented” does not mean a route is enabled in every environment, and “Foundation” does not mean every domain scenario or external integration is complete. Refer to the service catalog for a condensed cross-domain view.
Related Articles
See Also
Keywords
- Service responsibility
- Service dependency
- Documentation maturity
Revision Information
- Last reviewed: 2026-07-14
- Owner: architecture-team
- Status: Draft