LeetDezine
Notification System
Initializing search
    • Home
    • Start Here
    • Concepts
    • Back of Envelope
    • Foundation
    • Ascent
    • Expedition
    • Summit
    • Battleground
    • Home
    • Start Here
    • Concepts
    • Back of Envelope
    • Foundation
    • Ascent
      • Notification System
        • System Requirements
        • Deep Dives
        • Final Design
        • Observability
      • Pastebin
    • Expedition
    • Summit
    • Battleground
    1. Home
    2. Ascent
    3. Notification System
    02

    Ascent · Case Study 1

    Notification System

    Design a notification system — push, SMS, and email delivery at 5M sends/sec. Multi-channel fan-out, retry/DLQ, scheduled delivery, fault isolation per provider.

    System Requirements
    Problem statement, functional requirements, back-of-envelope estimation, NFRs, API design, and base architecture.
    System OverviewFREstimationNFRAPIBase Architecture
    Open →
    Deep Dives
    Database selection, Kafka fan-out, per-channel workers, scheduling with jitter, retry/DLQ strategy, rate limiting, and fault isolation per provider.
    Kafka Fan-outPer-Channel WorkersRetry / DLQSchedulingFault Isolation
    Open →
    Observability
    SLIs and SLOs for a notification service, latency and availability measurement, alerting strategy, and error budgets.
    SLI / SLOAlertingError Budget
    Open →
    Final Design
    The complete architecture after all deep dives — every component justified, every tradeoff resolved.
    Final ArchitectureFull Diagram
    Open →