Part 6 of 10: Reliable background jobs in Node.js, from zero .
By Sandro Dezerio , senior full-stack engineer.
The sign-up example is the one from Part 1 , Part 2 , Part 3 , Part 4 , and Part 5 . The numbers in this post come from a test that starts and kills real processes against a real Redis, not from a simulation. Tested with Node 22, BullMQ 6.5.3, ioredis 6.0.0, and Redis 7.
Every queue in this series so far has lived in the memory of the process that runs it. That works until the process stops. A deploy, a crash, or an out-of-memory kill empties the queue, and every sign-up still waiting for its welcome email is gone, with no error and no log line. This post moves the queue to Redis with BullMQ, and then kills the worker on purpose to see what survives.
What a restart does to an in-memory queue
The queue from Part 2 keeps its jobs in an array inside the Node.js process. When the process dies, the array dies with it.β¦