Workflow Architecture Overview
Summary
Workflow Service is a self-contained Minimal API bounded context with four code layers and shared-kernel dependencies. It is Transitional because its direct service surface is present while Gateway routing and cross-module terminal orchestration are not verified.
Implemented architecture
The API composes request handling. Commands own orchestration and return typed results. Aggregates enforce mutation rules. Infrastructure implements repository, tenant, audit, timeline, unit-of-work and outbox-store ports.
Dependency boundaries
The service references shared-kernel and contracts projects. Domain code does not depend on EF Core or ASP.NET Core. Application abstractions are implemented by Infrastructure. Queries intentionally use WorkflowDbContext directly.
Technical maturity
Core authoring and decision paths are implemented. Authorization, gateway ownership, advanced execution semantics, event consumers and broad automated coverage remain Foundation, Partial or Not implemented.
Limitations
There is no separate engine process, plug-in step executor, state-machine library, callback dispatcher or consumer registration in Workflow Service.
Requires Confirmation
Deployment topology, production ingress, broker consumers, scaling model and ownership of terminal updates require confirmation.
Source References
microservices/src/workflow-service/Program.csmicroservices/src/workflow-service/Api/WorkflowEndpoints.csmicroservices/src/workflow-service/Application/Commands/WorkflowInstanceCommands.csmicroservices/src/workflow-service/Infrastructure/WorkflowDbContext.csUI/salary-ui/apps/client-hrms-portal/src/pages/admin/OperationsAdminPages.tsx
Related Articles
See Also
Keywords
Workflow architecture, approval engine, Workflow Service, technical foundation.
Revision Information
- Status: Draft
- Last reviewed: 2026-07-20
- Next review: 2026-10-20