Event-Driven Notification Platform
A multi-tenant platform that accepts business events from any internal producer and decides what to notify, to whom, on which channel and when — then composes, dispatches and tracks the result across six channels. Producers publish facts; they know nothing about templates, channels or providers.
26 views, each in three formats.
Open a view to read it in full. Every SVG carries its diagram source inside it, so it opens in diagrams.net fully editable with no import step; the draw.io files are the same diagrams as plain source.
-
01
System Context
Who publishes events, who receives notifications, and where the platform boundary sits.
-
02
High-Level Architecture
The shape of the platform in one picture, for the reader who will see only one.
-
03
Layered Architecture
What depends on what, and the single dependency that points the wrong way.
-
04
Container and Component Architecture
Every deployable unit, its technology, its replica floor, and the protocol on every hop.
-
05
Integration and Interface Catalogue
Every way something enters or leaves the platform, with protocol, cadence and owner.
-
06
Channel Abstraction
The five-step contract every channel implements, and what differs between them.
-
07
Template and Content Lifecycle
How a message goes from draft to published, and how a bad one is taken back.
-
08
Multi-Tenancy and Noisy-Neighbour Control
What every tenant shares, what each one gets alone, and what stops one from hurting the rest.
-
09
Data Flow
Where data comes from, what it becomes at each stage, and the one stage where PII appears.
-
10
Event Topology and Priority Tiers
Which topics exist, why three tiers, how ordering is guaranteed, and how a stuck message gets out.
-
11
Data Architecture and Retention
What is authoritative, what is rebuildable, and how long each thing lives.
-
12
Core Data Model
The entities a decision reads and writes, and how they join.
-
13
Preference, Consent and Override Policy
Which notifications may ignore a stated preference, and on what authority.
-
14
Notification Orchestration
The seven questions asked of every event, in order, and what happens when the answer is no.
-
15
Event to Delivered Email
The happy path end to end, with the latency budget at each hop.
-
16
Timing, Scheduling and Digests
Six ways a notification can be timed, and the one due-work stream they all converge on.
-
17
Retry, Failover and Dead-Lettering
What happens when a provider says no, and how a message that cannot be sent stays recoverable.
-
18
Deployment and Failure Domains
What runs where, what survives a zone loss, and what a region loss actually costs.
-
19
Delivery Pipeline and Environments
How a change reaches production, and what stops a bad one.
-
20
Autoscaling, Capacity and Backpressure
What each tier scales on, where scaling stops, and what the platform does once it has stopped.
-
21
Observability and Operations
Every signal, where it goes, and how a support engineer answers the question in one place.
-
22
Administration and Operations Surface
What an operator can do, who may do it, and which actions are dangerous enough to gate.
-
23
The Operator Loop
How an alert becomes an answer, a fix and a clean backlog, without leaving a gap.
-
24
Security Architecture — Trust Zones
Where the boundaries are, what crosses them, and where an attacker actually arrives.
-
25
Identity and Access — Producer Authentication
How a producing workload proves who it is without ever holding a long-lived secret.
-
26
Failure Modes and Disaster Recovery
Everything that can break, what covers it, and the one trade-off deliberately accepted.
Everything as it was delivered.
These files are served exactly as they were produced — the diagram pages keep their own house style because that is the artifact, not a rendering of it.