Notification Architecture Diagram

Internal and outbound notification flow across CMS backend APIs, shared notification management, internal storage, asynchronous delivery channels, and observability controls

🔔

Business Events / Notification Consumers

EVENT SOURCES, API ACCESS & CONSUMERS

DOM

Domain Services

Generate business events that may require user-targeted internal or external notifications

Workflow Service

Triggers notifications on submission, approval, rejection, escalation, reassignment, and lifecycle transitions

API

CMS Backend APIs

Frontend-facing secured APIs expose notification retrieval and user notification actions with no dedicated BFF layer

React SPA

Displays in-app notifications, notification center content, and user state changes through secured backend APIs

USER

CMS User

Receives internal alerts and, where applicable, asynchronous outbound delivery

Notification events are generated by backend domain and workflow services, then routed into a shared notification service rather than being handled separately inside each feature service.

SHARED NOTIFICATION MANAGEMENT LAYER

Central service for creating, classifying, storing, exposing, and delivering notifications across CMS while keeping outbound delivery asynchronous

Notification Service

Receives internal event triggers and manages the full notification lifecycle as a reusable platform capability

GEN

Notification Generation

Builds message content, event type, target recipients, context, and priority

RULE

Channel Decision Logic

Determines whether the notification is internal only or also requires external delivery

STAT

Status Tracking

Tracks pending, queued, delivered, failed, read, unread, and retried notification states

RTR

Retry / Recovery Logic

Handles failed outbound attempts, retry handling, and recovery reprocessing without blocking business flows

Notification state is stored as application-owned operational data in DocumentDB, while the React UI retrieves user notifications through secured CMS backend APIs.

INTERNAL NOTIFICATION STORAGE & PRESENTATION

Notification Store in DocumentDB

Stores notification records, recipient targeting, read flags, delivery state, audit references, and lifecycle tracking data

API

Notification Retrieval APIs

Backend APIs expose user-specific notification reads, unread counts, and state updates securely to the frontend

CTR

Notification Center UI

Displays in-app notifications, unread state, alerts, and actionable messages in the CMS interface

SYNC

Secure In-App Flow

React SPA retrieves and updates notification state only through secured backend APIs, never through direct store access

Selected notifications can also be sent through an external channel, but outbound delivery remains asynchronous so it does not block core business transactions or workflow progress.

OUTBOUND DELIVERY CHANNEL

Infobip

Outbound delivery provider used for email-based notification delivery outside the CMS interface

OUT

Asynchronous Delivery Flow

Selected notifications are sent asynchronously so outbound delivery does not block protected CMS business operations

ACK

Delivery Acknowledgement

Delivery responses, failures, and outcome feedback are captured and mapped back into internal notification status

SECURITY, CONTROL, AND OBSERVABILITY

Azure AD Context

Identity and token context are used to resolve recipients and support secure notification access

RBAC

Backend Authorization

RBAC and ABAC are enforced directly in backend services for notification generation, retrieval, and recipient-specific access

Datadog

Collects logs, metrics, traces, failures, retry behavior, and delivery-health signals for notification operations

AUD

Operational Auditability

Notification generation, delivery attempts, read state, and failure paths remain observable and traceable end to end

END-TO-END OUTCOMES

In-App Notification Created

A user-targeted internal notification is stored in DocumentDB and becomes visible in the CMS UI

MAIL

Outbound Email Sent

An external email notification is sent through Infobip when required by configured channel rules

STAT

Delivery Status Updated

Notification records reflect success, failure, retry state, and read or unread progress

TRACE

Flow Observable

Notification behavior remains monitorable and auditable across both internal UI and outbound delivery paths

          Event sources, API access & consumers
          Shared notification management
          Internal storage & presentation
          Outbound delivery channel
          Security & observability controls
          End-to-end outcomes
        