NODE.JS WORKER THREADS ARE PROBLEMATIC, BUT THEY WORK GREAT FOR US

Summary from the TLDR Dev newsletter

Inngest encountered event loop starvation in its Node.js-based Connect service, where CPU-heavy user code blocked critical heartbeats, causing "no available worker" errors. Their solution was to move the Connect service's internals, like WebSocket connections and heartbeats, into a separate Node.js worker thread to isolate them from user code execution.