Urgent.News

What's breaking now, across thousands of outlets.

Tech

Handle Rate-Limited Webhook Subscriptions with Push Queues — A Practical Node.js Drain

The safest way to handle rate-limited webhook subscriptions in Node.js push queues is to make draining a state transition, not a shutdown command. Stop admitting new work, finish only attempts with a known owner, and move every uncertain outcome into a durable reconciliation path. In a property-management system, a queue reaching zero is not proof that lease, maintenance, or tenant-integration…

Handling rate-limited webhook subscriptions in Node.js push queues can be achieved by treating draining as a state transition rather than a shutdown command. This approach involves stopping the admission of new work, finishing only attempts with a known owner, and moving every uncertain outcome into a durable reconciliation path.

By using a stable operation key for every retry and preserving the business event separately from its delivery attempts, at-least-once delivery can be achieved while maintaining an exactly-once mindset. The key question to ask is not how quickly the pool empties but which outcomes the system can prove and which must remain unresolved, thus transforming the drain from a queue operation into an auditable workflow.

Brief written by urgent.news from Dev.to's own syndicated text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

When Upstream Disappears: Building a Dependency Safety Net with Lockfiles, Proxy Caches and Git Mirrors

Tuần này trên Hacker News có tin repo ONNX Runtime của Microsoft biến mất khỏi GitHub. Chưa cần biết lý do là gì, câu hỏi mình đặt ra ngay là: nếu sáng mai một dependency quan trọng của team mình bị…

  • Use lockfiles and hashes to ensure exact dependency versions
  • Set up private proxy cache for package registries
  • Mirror important Git repositories to maintain code versions

Stop Guessing: Measure Your Flaky Test's Reproduction Rate First

Ask a team about their worst flaky test and you will get an opinion: "it fails sometimes," "it's the checkout one, it's really bad," "just re-run it, it always passes the second time." None of those…

  • Measure flaky test reproduction rate, not opinions
  • Run test multiple times on real CI runner
  • Count passes and failures, log results

More from Wednesday 18 November →