Observed Signal · Jul 13, 2026 · Technical Release · Source: DEV Community · Impact: 1/5 · Sentiment: Positive
Making Webhook Delivery Resilient with a Delivery Layer
The article explains how direct webhook integrations fail when receivers are offline and describes a resilient architecture that inserts a persistent delivery layer (Adal) between webhook providers and receivers. Adal accepts and stores incoming webhooks at a permanent HTTPS endpoint, provides delivery history and retries, and can forward events via Direct HTTP to public endpoints or via an outbound WebSocket tunnel (Adal CLI) to private/local services. If automatic retries are exhausted, stored events remain available for manual redelivery during their retention period. The article also covers idempotent receiver design, signature validation, encrypted storage, and the importance of complying with network and security policies when using an intermediary.
Practical engineering guidance and a specific SaaS transport approach for webhook reliability; useful for developer tooling but not industry-shifting.
MARKET SIGNALS
Track Infrastructure Signals & Market Shifts
Polaris7 connects regulatory filings, primary sources, leadership changes, and M&A activity into structured intelligence. Set up your Polaris7 workspace to monitor relevant companies in your executive briefing.
- Verified primary sources
- Automated briefings
- Instant watchlist setup
Key Takeaways & Evidence Grounding
- Adal receives and stores incoming webhooks at a permanent HTTPS endpoint before attempting delivery to the final receiver.
- Adal supports two delivery methods: Direct HTTP for public endpoints and Adal CLI (an outbound WebSocket tunnel) for private or local services.
- Each destination has configurable automatic retries; if retries are exhausted the webhook remains stored until its retention period expires and can be redelivered manually.
- Adal stores webhook contents in encrypted form and identifies itself in the User-Agent header when forwarding requests.
Ontology Mapping & Concepts
Related Market Signals & Shifts
Recent verified developments and strategic activity across this market segment.
How I Built a Reliable Webhook Delivery System
A developer describes building a production-grade webhook delivery system using FastAPI, PostgreSQL and Redis to solve common reliability issues. The post explains design changes: make delivery asynchronous (return 202 Accepted), add a watchdog to requeue stale IN_FLIGHT jobs, implement exponential backoff retries via a Redis sorted-set delay queue, apply a per-subscription circuit breaker (5 failures, 60s cooldown) and sign payloads with per-subscription HMAC‑SHA256 verified with hmac.compare_digest. Observability is provided with Prometheus and Grafana. The author reports achieving 99.9% delivery reliability across 10,000+ daily webhooks and promises a deeper technical deep-dive later.
Safe Webhook Idempotency Prevents Duplicate Deliveries
The article explains why duplicate webhook deliveries are common (network failures, timeouts, retries) and recommends explicit idempotency handling to prevent repeated side effects like duplicate orders, payments, or emails. It defines idempotency keys as unique identifiers sent by the provider or added by an intermediary, and describes the need for atomic reservation of keys (uniqueness enforced at the database level) to handle concurrent deliveries safely. A PostgreSQL example uses a processed_webhooks table and INSERT ... ON CONFLICT DO NOTHING to detect repeats. Retention of idempotency keys should match providers' retry windows. The webhook platform Adal can add an X-Adal-Idempotency header when forwarding webhooks to help consumers distinguish retries from replays.
Successful HMAC Shows Signed Webhook Data Preserved
A production payment webhook was forwarded through an intermediary delivery layer (Adal Server → Adal CLI) and then verified by the final handler; the HMAC verification succeeded. The article explains that a successful HMAC check is strong evidence that the values included in the provider's signed message (often the raw request body, possibly plus a timestamp or selected metadata) were preserved end-to-end, but it does not prove that every HTTP header or transport detail remained byte-for-byte identical. The post emphasizes preserving raw request bytes, forwarding all signature-covered values, performing verification at the final trust boundary, using constant-time comparisons, and testing the full delivery route with real provider events.
WATCHLIST & BRIEFINGS
Receive future signals for Infrastructure in your Watchlist briefing
Stay ahead of material M&A deals, leadership changes, account wins, and product rollouts. Polaris7 connects primary filings, company newsrooms, and trade reporting directly into your executive briefing.
- Regular primary-source checks
- Structured Watchlist briefings
- Preserves current context
Market Signal Monitoring
Follow affected companies in Polaris7 with regular source checks and structured Watchlist briefings.
Monitor Infrastructure
Follow affected companies in Polaris7 with regular source checks and structured Watchlist briefings.
