Event-Driven Notification Platform · View 09 of 26 · 3 · Data

Data Flow

Where data comes from, what it becomes at each stage, and the one stage where PII appears.

Editable source SVG draw.io All views

Three domains, kept separate

Event data — what happened, owned by the producer, immutable once accepted
Notification data — what the platform decided, owned by the platform, including decisions to send nothing
Delivery data — what happened while trying, high volume, analytical rather than transactional

The PII boundary

Events carry a subject reference, never an email address, phone number or device token
Contact details are resolved inside the Render Service at send time and held in memory only
An erasure request purges the vault; event and notification records survive with an unresolvable reference, so metrics and audit stay intact

Cadence

Producer to bus: synchronous with acks=all, acknowledged in under 80 ms at p95
Bus to archive: five-minute micro-batch into Iceberg
Attempts to ClickHouse: asynchronous per attempt, batched at 1 s or 10 000 rows

◀ Multi-Tenancy and Noisy-Neighbour Control All views Event Topology and Priority Tiers ▶