This article discusses two approaches to running background jobs in Node.js applications - the classic queue & workers approach and a simpler approach using HTTP and Inngest, a serverless job scheduler. The traditional method involves setting up a message queue and multiple worker processes, which can be complex and time-consuming. On the other hand, Inngest allows developers to send events directly to their functions without needing a separate queue or workers. This approach is more straightforward and requires less setup, making it ideal for smaller applications. However, there are limitations to this HTTP-based approach, such as potential extra load on the backend server and timeouts. The article concludes by encouraging readers to try Inngest and stay updated on future platform support.