Post

Matteo Collina
@nodeland.dev

Node.js doesn't have a predictive way to manage traffic spikes, so over-provisioning for peak loads isn't optimized for the stable periods that follow. We've all faced this issue. This is why Platformatic is simplifying multithreading in our Node.js app server. 🧵 https://buff.ly/48yJoHD

youtu.beAddressing Overprovisioning & Performance Issues in Node.js via Multiple WorkersWe know scaling Node.js efficiently can be challenging—especially with the infrastructure costs that come from handling unpredictable traffic spikes. With Pl...
Matteo Collina
@nodeland.dev

Node.js applications are usually deployed as single-threaded: ↳Each instance operates as a single process. ↳Organizations overprovision to handle traffic spikes. ↳This leads to wasted resources and increased costs.

Matteo Collina
@nodeland.dev

What’s clear is that we need to rethink our approach to infrastructure. This is why Platformatic’s Watt app server now supports service replication. By starting multiple workers, you can now fully utilize all the CPU cores available on your server, providing the best possible user experience.

0 reposts0 likes

Matteo Collina
@nodeland.dev

Most importantly, this is all done without requiring any code changes on your part. What does this mean for your application’s performance? Hint: it’s great news.

Matteo Collina
@nodeland.dev

Upon examining the top data, we found that only 3 out of the 10 available cores were actually utilized. We then repeated the test, increasing the number of `workers` to 2, and here are the results: