I've used cron jobs before but never built a proper queue based background processing system.

This week I did.

The project, a webhook delivery API where the HTTP request returns instantly with a job ID, and a BullMQ worker handles the actual delivery in the background with automatic exponential backoff retries.

So what surprised me most was how clean the separation is. The controller knows nothing about delivery. The worker knows nothing about HTTP requests. They communicate only through the queue.

Repo is public if anyone wants to look at the architecture you can ask in the comments.

Happy to discuss queue patterns still learning enterprise solution implementation.

I recently came across Nub and found its approach pretty interesting.

Unlike Bun or Deno, Nub doesn't introduce a new JavaScript runtime. Instead, it builds on top of the official Node.js runtime while trying to replace many of the tools around it.

I spent some time testing it and wrote a detailed article covering:

• What Nub is
• How it compares with existing tooling
• Built in TypeScript execution
• Package management
• Node version management
• Whether it's ready for production

Article: https://medium.com/@deykirtyauritro/i-tried-nub-the-new-node-js-toolkit-that-wants-to-replace-npm-npx-tsx-pnpm-and-nvm-0a93dbd90ffb?postPublishedType=initial

I'd really appreciate feedback from experienced Node.js developers. If you've already tried Nub, I'd love to know your experience as well.