LeetDezine
Deep Dives
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
          • Database
          • Kafka
          • Per-Channel Workers
          • Scheduling
          • Retry And DLQ
          • Rate Limiting
          • Fault Isolation
        • Final Design
        • Observability
      • Pastebin
    • Expedition
    • Summit
    • Battleground
    1. Home
    2. Ascent
    3. Notification System
    4. Deep Dives
    DD

    Notification System · Deep Dives

    Deep Dives

    Seven deep dives — database, Kafka fan-out, per-channel workers, scheduled dispatch, retry/DLQ, rate limiting, and fault isolation.

    Database
    DB selection for notification storage and schema design for high write throughput.
    CassandraSchemaWrite Throughput
    Open →
    Kafka
    Queue selection rationale and Kafka fan-out design for multi-channel delivery.
    KafkaFan-outQueue Selection
    Open →
    Per-Channel Workers
    Push, SMS, and email worker architecture — isolation, third-party adapters, and failure containment.
    PushSMSEmailWorker Isolation
    Open →
    Scheduling
    Scheduled notifications, naive approaches, scheduler DB design, jitter, and dispatch flow.
    Scheduler DBJitterDispatch Flow
    Open →
    Retry & DLQ
    Retry strategy with exponential backoff, dead letter queue design, and failure handling.
    RetryDLQBackoffFailure Handling
    Open →
    Rate Limiting
    Per-provider rate limiting to avoid throttling APNs, FCM, and SMS gateways.
    APNsFCMProvider Throttle
    Open →
    Fault Isolation
    APNs down, Cassandra down, Kafka down, Redis down, and Scheduler down — each failure isolated.
    APNs DownKafka DownCassandra DownCircuit Breaker
    Open →