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

High-Level Architecture

The shape of the platform in one picture, for the reader who will see only one.

Editable source SVG draw.io All views

Decisions

Ingestion acknowledges after a durable Kafka write, not after a decision — producers are never blocked by rule evaluation
Rules are evaluated once, centrally, in a stateful stream job; channel workers make no routing decisions
Every channel is a consumer of its own topic, so one slow provider cannot back up another

Targets

Event ingestion acknowledged p95 under 80 ms, p99 under 100 ms
Event to notification queued p95 under 800 ms
Event to provider accepted p95 under 2 s for transactional traffic
99.95% availability on ingestion, 99.9% on the platform as a whole

Deliberately omitted

Retry, channel fallback and dead-lettering — views 17 and 26
Scheduling, digests and quiet hours — view 16
Everything about tenancy and isolation — view 08

◀ System Context All views Layered Architecture ▶