Node.js worker threads in production

The blog article by Aaron Harper discusses the implementation of Node.js worker threads in the production environment of Inngest Connect to maintain connection health independent from potentially blocking user code. The transition involved moving critical components like the WebSocket connection, heartbeat timer, reconnect logic, and lease extension logic into a separate event loop handled by a worker thread, while user code remained on the main thread. This separation required careful design considerations, such as defining clear API boundaries with postMessage, converting callbacks into a request-response protocol, and ensuring all data exchanged between threads is structured-clone safe. Additionally, the article highlights the importance of creating robust systems around the worker threads, including message protocols, logger proxying, crash recovery, and graceful shutdown processes. This approach ensures that critical timers and connection management tasks continue to function even if the main thread is busy, ultimately enhancing the reliability and stability of the Connect service.