That has nothing to do with node. You have a lot of situations where a dedicated job queue makes sense
Go has lots of mature in-process queue systems, yet River exists, because in lots of situation it makes perfect sense to have your job queue in its own process
It's missing lots of features like sleeping on waits, warm starts etc.