Event-Driven Notification Platform · View 04 of 26 · 2 · Structure

Container and Component Architecture

Every deployable unit, its technology, its replica floor, and the protocol on every hop.

Editable source SVG draw.io All views

Decisions

Four planes — edge, decision, composition, delivery — each scaling on its own signal
Rendering is a separate service from orchestration so a template change never redeploys the decision plane
Recipient Profile is the only component allowed to read the PII vault; everything else passes a reference

Technology choices and the alternative

Flink over Kafka Streams: windowing, broadcast rule state and independent scaling of the rule job
Temporal over a database-backed scheduler: durable timers, retries and multi-step fallback for free
Go over Java for workers: startup time and memory footprint at 600 pods at peak
ClickHouse over PostgreSQL for delivery attempts: about 1 billion rows a day would not fit the relational store

Assumptions

Pod counts are the steady-state floor at 5 000 events/s and are validated by the staging load test, not by calculation
Kafka runs on the same cluster as the workloads with dedicated node pools; a separate cluster is the fallback if noisy-neighbour tests fail

◀ Layered Architecture All views Integration and Interface Catalogue ▶