Node.js: More Threads Than You Think
February 20 @ 12:00 pm - 1:00 pm
Node.js was announced in 2009 as a single-threaded JavaScript runtime. In 2018, it became multi-threaded, and no one noticed. What can worker_threads do? What are they useful for? What’s the best way of communicating between two threads? Scaling Node.js applications efficiently has long been a challenge for teams. Traditionally, Node.js runs on a single thread per service, meaning each instance operates as a single process within its container. This forces teams to overprovision infrastructure to handle unpredictable traffic spikes, leading to wasted resources and increased costs. The single-threaded nature of Node.js can pose performance risks; if a thread blocks its event loop due to a computationally heavy operation or a sudden traffic spike, it can cause downtime or degrade user experience. This raises a crucial question: How can teams optimize Node.js resource utilization to reduce costs without compromising performance or risking downtime? In this talk, we will explore multi-threaded Node, showing devs what they need to know to properly leverage multithreading.
About the Speaker
With over 15 years of software engineering experience, Matteo is known throughout the open source community for his work authoring the Fastify web framework, the fast logger Pino, and his contributions to Node.js. Matteo is a member of the Node.js Technical Steering Committee and is an active open source author in the JavaScript ecosystem, with modules he maintains being downloaded over 12 billion times per year.
About the Open Source Architect Community
The Open Source Architect (OSA) Community is an invitation-only group for seasoned software architects who are passionate about open source technology. For the latest updates on all things open source, follow our public feed on LinkedIn.