Node.js Consumer Capacity: Webhook Delivery, Rate Limits, and Dead-Letter Decisions
Short answer: treat a renewal reminder's business deadline as the primary SLO, then make the Node.js consumer's rate limit, acknowledgement boundary, retry policy, and dead-letter path one explicit contract. That rule matters because a B2B SaaS renewal campaign can look healthy at the transport layer while its reminders are already too late. A successful HTTP response is evidence about delivery,…
The article emphasizes the importance of treating a renewal reminder as a business deadline, which should be the primary Service Level Objective (SLO). The Node.js consumer must establish a contract regarding rate limits, acknowledgement boundaries, retry policies, and dead-letter paths. The consumer should validate the request at the HTTPS endpoint, persist state for replayability, and acknowledge only after the durable business transition succeeds.
In case of transient dependencies or quota responses, the consumer should nack with bounded backoff. Malformed envelopes or deterministic validation failures should be directed to dead letters. The event envelope should include an event ID, subscription ID, business deadline, and schema version. By keeping mutable customer data behind identifiers, a retry represents the same intended action rather than an obsolete snapshot.
At-least-once delivery makes duplicate handling an application responsibility, which should be managed through a uniqueness constraint on the event ID or business key, ensuring the duplicate check and reminder write occur in one transaction.
Brief written by urgent.news from Dev.to's own syndicated text. Machine-written — may contain errors; check the original before relying on it.
