Event-Driven Notification Platform · View 01 of 26 · 1 · Context and scope

System Context

Who publishes events, who receives notifications, and where the platform boundary sits.

Editable source SVG draw.io All views

In scope

Accepting business events from any internal producer, validated against a registered schema
Deciding what to notify, to whom, on which channel and when
Composing, dispatching and tracking notifications across six channels to the point a provider accepts them

Out of scope

Producing the business events — each domain service keeps that responsibility
Owning customer contact data — Customer Master stays the system of record; the platform holds only what it needs to send
Anything after the provider accepts: inbox placement, carrier routing, device delivery

Stated assumptions

Multi-tenant from day one; single-tenant would remove roughly a third of this design
5 000 events/s normal, 25 000 peak, fan-out 1.8, so about 750 M notifications a day
Keycloak is the identity provider for producers and administrators alike
GDPR and CCPA apply; audit retention 7 years

All views High-Level Architecture ▶