Orchestration Layer Diagram
BFF / orchestration responsibilities, UI-facing coordination, downstream service interaction, data dependencies, and cross-cutting controls in the CMS platform
👥
CMS Users / React UI
FRONTEND REQUEST CONTEXT
UI
React SPA
Sends UI-driven requests and receives aggregated 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, user identity context, and requested screen composition
The frontend does not coordinate all backend interactions directly. Requests are shaped and routed through the orchestration layer.
BFF / ORCHESTRATION LAYER
Central coordination point for UI-facing APIs, response shaping, and multi-service interaction
API
API Facade
Single frontend-facing entry point for CMS screen requests
AGG
Response Aggregation
Combines data from multiple services into one UI-ready payload
VM
View Model Builder
Shapes service responses into frontend-friendly screen models
ROUT
Service Coordination
Directs requests to the correct domain and shared platform services
ERR
Error Normalization
Standardizes error handling and service-response formatting
AUTH
Auth Context Propagation
Passes identity and access context downstream for protected operations
WF
Workflow Coordination
Coordinates submission, approval, and tracking flows across services
DOC
Document Flow Coordination
Coordinates upload, metadata lookup, and secure file retrieval workflows
The orchestration layer calls the appropriate backend services and merges their outputs into one coherent response per UI scenario.
DOWNSTREAM SERVICES COORDINATED BY THE BFF
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, and transitions
NT
Notification Service
In-app notifications and outbound delivery coordination
DOC
Document Management Service
Upload, download, metadata resolution, and file linkage
DATA & PLATFORM DEPENDENCIES
FAB
Microsoft Fabric
Read-only enterprise data source used by backend services for dashboards, summaries, and analytical reads
DDB
Azure DocumentDB
Operational persistence for workflow state, notification state, preferences, and file metadata
ADLS
ADLS Gen2
Binary storage for uploaded files, attachments, generated documents, and downloadable artifacts
CROSS-CUTTING CONTROLS APPLIED THROUGH THE ORCHESTRATION PATH
AAD
Azure AD Context
Authentication tokens and user identity context arrive before protected BFF actions
RBAC
RBAC / ABAC
Authorization is enforced server-side and propagated to downstream services
DD
Datadog
Logs, traces, metrics, and operational signals from orchestrated request flows
IB
Infobip
Outbound delivery path used when notification flows require external communication
WHY THE ORCHESTRATION LAYER EXISTS
1
Reduce Chatty UI Calls
The frontend avoids calling many services directly for one screen
2
Centralize UI Logic
Screen composition stays out of domain services and out of the browser
3
Stabilize API Contracts
Frontend gets consistent payloads even when downstream services evolve
4
Coordinate Cross-Service Flows
Workflow, documents, notifications, and dashboards can be composed coherently
Frontend request context
BFF / orchestration responsibilities
Downstream service landscape
Data & platform dependencies
Cross-cutting controls
Purpose / benefits of orchestration