Orchestration Layer Diagram

Request coordination responsibilities across secured CMS backend APIs, domain services, shared platform services, data dependencies, and cross-cutting controls in the CMS platform
👥
CMS Users / React UI
FRONTEND REQUEST CONTEXT
React
React SPA
Sends UI-driven requests and receives secured backend responses
SCR
Screen Modules
Dashboard, profile, roster, attendance, workflow, documents, and notifications
ACT
User Actions
Search, view, submit, upload, approve, reject, and update actions
CTX
UI Context
Filters, pagination, identity context, and requested screen composition
The frontend does not coordinate backend dependencies directly. Requests are sent to secured CMS backend APIs, where routing and orchestration happen inside backend services.
BACKEND REQUEST ORCHESTRATION LAYER
Coordination responsibilities performed by secured CMS backend APIs and service logic rather than by a dedicated BFF component
API
CMS Backend APIs
Frontend-facing secured API layer for CMS screen requests with no dedicated BFF
AGG
Response Aggregation
Combines results from multiple backend services into coherent UI-facing responses where needed
VM
Response Shaping
Shapes service outputs into frontend-friendly payloads and screen-ready data structures
ROUT
Service Routing
Routes requests to the correct domain services and shared platform services
ERR
Error Normalization
Standardizes error handling and service-response formatting for frontend consumers
AUTH
Auth Context Propagation
Passes identity, claims, and request context downstream for protected operations
WF
Workflow Coordination
Coordinates submission, approval, routing, and tracking flows across backend services
DOC
Document Coordination
Coordinates upload, metadata resolution, and secure retrieval flows through document services
Backend orchestration calls the appropriate services and merges their outputs into one coherent response per UI scenario without requiring a separate orchestration-only deployable.
DOWNSTREAM SERVICES
PRO
Profile Service
Profile context and user-specific summary data
ROS
Roster Service
Schedules, assignments, and related roster views
ATT
Attendance Service
Attendance metrics, events, and related status
PRD
Productivity Service
Operational KPI and productivity-related outputs
EVT
Events Service
Operational events and event-driven screen content
WF
Workflow Management Service
Workflow lifecycle, approvals, tracking, transitions, and routing control
NT
Notification Service
In-app notifications, delivery state, and outbound notification coordination
DOC
Document Management Service
Upload, download, metadata resolution, file linkage, and secure retrieval control
DATA & PLATFORM DEPENDENCIES
Microsoft Fabric
Microsoft Fabric
Read-only enterprise data source used by backend services for dashboards, summaries, and analytical reads
Azure DocumentDB
Azure DocumentDB
Operational persistence for workflow state, notification state, preferences, and file metadata
Azure Storage Account (Blob Storage)
Azure Storage Account (Blob Storage)
Binary storage for uploaded files, attachments, generated documents, and downloadable artifacts
CROSS-CUTTING CONTROLS
Azure AD
Azure AD Context
Authentication tokens and user identity context arrive before protected backend actions
RBAC
RBAC / ABAC
Authorization is enforced directly in backend services for APIs, workflows, document access, and protected business actions
Datadog
Datadog
Logs, traces, metrics, and operational signals from orchestrated backend request flows
Infobip
Infobip
Outbound delivery path used when notification flows require external communication
WHY THIS ORCHESTRATION APPROACH EXISTS
1
Reduce Chatty UI Calls
The frontend avoids calling many services directly for one screen or business scenario
2
Keep UI Logic out of the Browser
Screen composition and coordination stay in secured backend layers rather than in the client
3
Stabilize API Contracts
Frontend gets consistent payloads even when downstream backend services evolve
4
Coordinate Cross-Service Flows
Workflow, documents, notifications, and dashboard scenarios can be composed coherently across services
Frontend request context Backend orchestration responsibilities Downstream service landscape Data & platform dependencies Cross-cutting controls Purpose / benefits of orchestration
This orchestration layer diagram shows where request coordination happens in the CMS architecture, what responsibilities are handled by secured backend APIs and services, which services are coordinated, and why orchestration remains part of the backend architecture without a separate BFF component.