Backend Engineer: Merancang Hub API Notifikasi & Pesan Asinkron Multi-Saluran

Mengirimkan email transaksional, kode OTP SMS, pesan WhatsApp, dan notifikasi Web Push secara sinkron di dalam handler HTTP membuat latensi API menjadi lambat dan rentan gagal saat penyedia hulu (AWS SES, Twilio, atau FCM) membatasi laju permintaan. Lebih buruk lagi, percobaan ulang (retry) yang naif dapat mengirimkan 5 pesan konfirmasi ganda kepada pelanggan. Sebagai Backend Engineer dan Cloud Engineer, saya merancang hub notifikasi asinkron multi-saluran yang idempoten dengan failover penyedia otomatis, circuit breaker per saluran, dan pelacakan status pengiriman terpadu.

1. Fan-Out Saluran Idempoten & Rantai Failover Penyedia

Setiap permintaan notifikasi masuk ke hub dengan idempotency_key deterministik (misalnya order_shipped:{order_id}:email) sebelum didistribusikan ke antrean masing-masing saluran. Apabila penyedia utama mengembalikan kesalahan 5xx atau mengalami timeout, circuit breaker secara otomatis mengalihkan pengiriman ke penyedia cadangan tanpa memicu pengiriman ganda:

from dataclasses import dataclass
from enum import Enum

class ChannelType(str, Enum):
    EMAIL = "EMAIL"
    WHATSAPP = "WHATSAPP"
    WEB_PUSH = "WEB_PUSH"

@dataclass(frozen=True)
class NotificationEnvelope:
    idempotency_key: str
    tenant_id: str
    recipient_id: str
    channel: ChannelType
    template_slug: str
    context_vars: dict

async def dispatch_with_provider_failover(
    envelope: NotificationEnvelope,
    primary_adapter: object,
    fallback_adapter: object,
    ledger_repo: object,
) -> str:
    if await ledger_repo.already_dispatched(envelope.idempotency_key):
        return "DUPLICATE_SKIPPED"

    try:
        provider_msg_id = await primary_adapter.send(envelope)
        provider_used = primary_adapter.name
    except ProviderTransientError:
        provider_msg_id = await fallback_adapter.send(envelope)
        provider_used = fallback_adapter.name

    await ledger_repo.record_sent(
        idempotency_key=envelope.idempotency_key,
        provider=provider_used,
        provider_msg_id=provider_msg_id,
    )
    return f"SENT_VIA_{provider_used}"

2. Penanganan Webhook Bounce/Complaint & Perlindungan Reputasi Pengirim

Menjaga tingkat keterkiriman kotak masuk di atas 99% pada AWS SES menuntut pemrosesan webhook bounce dan complaint secara real-time. Hub kami memproses notifikasi pengiriman melalui pipeline webhook idempoten dan topologi Dead-Letter Queue AWS SQS untuk segera menghentikan pengiriman ke alamat email yang tidak valid. Kunjungi Layanan Sprint Teknik 1 Hari untuk membangun arsitektur notifikasi Anda.


About the Author — Hire Aldian Fazrihady (Cloud Engineer, GCP Professional Cloud Architect, GCP Professional Data Engineer, Backend, AI & Full Stack Engineer)

Aldian Fazrihady is a Top-Rated Senior Cloud Engineer, GCP Professional Cloud Architect (Google Cloud Certified), GCP Professional Data Engineer (Google Cloud Certified), Backend Engineer (Python, Django, FastAPI, Go, PostgreSQL), AI Application Engineer (LLMs, RAG, MCP, Google ADK, LangGraph), and Full Stack Engineer (React, Next.js, TypeScript) with 15+ years of production software engineering experience.

Hire Aldian Fazrihady on Upwork | Book 1-Day Programming Service ($100 USD / Rp 1.000.000) | View Live AI Portfolio | Send a Direct Message

Related Engineering Articles

Engineering Role Pillar Guides & Category Hubs