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

Channel Abstraction

The five-step contract every channel implements, and what differs between them.

Editable source SVG draw.io All views

The contract

Resolve address, render, throttle, dispatch, confirm — five methods, one interface
The core platform knows the interface and nothing about SMTP, SMPP, APNs or Block Kit
Adding voice or WhatsApp is one adapter and one provider client, with no change above the delivery plane

What genuinely differs

Throttling is per-channel physics: carrier TPS for SMS, per-device rate for push, endpoint capacity for webhooks
Confirmation ranges from a synchronous 250 for SMTP to an asynchronous DLR minutes later for SMS
Only email and SMS carry a real delivery receipt; the others confirm acceptance only, and the dashboards say so

Deliberately omitted

Voice, deferred to phase 2 — the contract already fits it
Retry behaviour, which is common across adapters and lives on view 17

◀ Integration and Interface Catalogue All views Template and Content Lifecycle ▶