Preventing Duplicate Weekly Digest Webhooks After Queue Lease Timeouts in Node.js
A design guide argues that delayed weekly webhook deliveries should separate scheduling from delivery, using a durable delivery record and a lease shorter than the queue timeout. It recommends a single idempotency key across all retries, since a timeout does not confirm whether the receiver got the request. The author uses a hypothetical 100,000-customer workload with an assumed 2% retry rate to show that duplicate attempts drive costs more than the schedule itself. The guide advises storing only compact delivery outcomes rather than full payloads, accepting that regenerating payloads during investigations will be slower. It also stresses renewing leases with a cap and keeping the HTTP deadline inside the remaining lease window.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in