Integration Architecture Diagram

Crew Management System – upstream source integrations, enterprise data platform, secured CMS backend APIs and services, operational data stores, and external support services with protocol, frequency, and interaction model
Source Systems
Enterprise Data Platform
CMS Integration Layer
Application Data Stores
External Support Services
Source Systems
Upstream Enterprise Sources
Netline Crew Source-to-platform transfer via SFTP / XML
Frequency: every 30 minutes
Nature: asynchronous batch feed
Training Insight Source-to-platform transfer via SFTP / XLSX
Frequency: daily
Nature: asynchronous file-based feed
Recruitment Insight Source-to-platform transfer via SFTP / XML
Frequency: twice daily
Nature: asynchronous batch feed
Oracle Source-to-platform transfer via SFTP / ENC
Frequency: daily
Nature: asynchronous secure file feed
Enterprise Data Platform
Data Platform / Fabric Ingestion
Platform Ingestion Layer Receives upstream feeds, applies enterprise-controlled ingestion processes, and prepares data for curated use
Microsoft Fabric Curated enterprise analytical datasets consumed by CMS as a read-only source
Main Role
Fabric acts as the enterprise system of insight for CMS reads, not as the transactional operational store for workflow state, notification state, preferences, or file metadata.
CMS Integration Layer
Presentation + API Access
React SPA Protocol: HTTPS / REST JSON
Nature: synchronous UI requests
CMS Backend APIs Protocol: HTTPS / REST JSON
Nature: synchronous frontend-facing secured API layer with no dedicated BFF
Core CMS Services
Profile Service
REST / sync
Roster Service
REST / sync
Attendance Service
REST / sync
Events Service
REST / sync
Leave Service
REST / sync
Trainings Service
REST / sync
Qualifications Service
REST / sync
Recruitment Service
REST / sync
Productivity Service
REST / sync
Shared Platform Services
Workflow Mgmt Service
REST / sync for submission, routing, transition, and query
Notification Service
Internal async trigger + outbound delivery integration
Document Mgmt Service
Controlled upload / retrieval + metadata handling
Integration Principles
CMS backend APIs route requests to domain and shared platform services without a separate BFF layer.
Backend services enforce RBAC and ABAC directly for protected APIs, workflows, and document actions.
Application Data Stores
Operational Stores
Azure DocumentDB Protocol: application data access
Nature: synchronous operational persistence for workflows, notifications, preferences, audit records, and file metadata
Azure Storage Account (Blob Storage) Protocol: backend-controlled file/object access
Nature: upload / download and artifact storage for binary files, attachments, and exports
Data Responsibility
Operational application state is intentionally separated from enterprise analytical reads and from binary file storage. DocumentDB stores application-owned metadata and state, while ADLS stores document content and generated artifacts.
External Support Services
Security, Delivery, and Observability
Azure AD Protocol: OIDC / OAuth2 token flow
Nature: synchronous authentication and token validation support
Infobip Protocol: outbound API integration
Nature: asynchronous email / notification delivery
Datadog Protocol: logs / metrics / traces ingestion
Nature: asynchronous observability and monitoring
Role in Integration Landscape
These services support authentication, outbound delivery, and observability across multiple CMS components without becoming part of the core domain model.
Netline Crew → Data Platform
Protocol: SFTP / XML
Frequency: every 30 minutes
Interaction type: asynchronous batch integration
Training Insight → Data Platform
Protocol: SFTP / XLSX
Frequency: daily
Interaction type: asynchronous file-based integration
Recruitment Insight → Data Platform
Protocol: SFTP / XML
Frequency: twice daily
Interaction type: asynchronous batch integration
Oracle → Data Platform
Protocol: SFTP / ENC
Frequency: daily
Interaction type: asynchronous secure feed
React SPA → CMS Backend APIs
Protocol: HTTPS / REST JSON
Interaction type: synchronous UI-to-secured-backend communication
CMS Backend APIs → Domain / Shared Services
Protocol: HTTPS / REST JSON
Interaction type: synchronous internal service calls and request routing
Domain Services → Microsoft Fabric
Protocol: backend-managed data access
Interaction type: synchronous read-only enterprise data retrieval
Workflow / Notification / Document Services → DocumentDB
Interaction type: synchronous operational persistence for application-owned state and metadata
Document Management Service → Azure Storage Account (Blob Storage)
Interaction type: controlled upload / download and binary file retrieval
Notification Service → Infobip
Interaction type: asynchronous outbound delivery integration
Frontend / Backend Services ↔ Azure AD
Protocol: OIDC / OAuth2 / token validation flows
Interaction type: synchronous authentication support
CMS Services → Datadog
Interaction type: asynchronous observability, monitoring, and telemetry export
Source systems Enterprise data platform CMS integration layer Shared / operational services Support services
This integration architecture separates upstream enterprise feeds, the curated data platform, secured CMS backend APIs and services, operational application stores, and external support integrations while explicitly showing protocol, frequency, and sync / async behavior.