I'm a NodeJS fanboy and I partially agree with this. Feel free to use NodeJS if it allows you iterate faster and your app doesn't need much load. If you're pl

I'm a NodeJS fanboy and I partially agree with this. Feel free to use NodeJS if it allows you iterate faster and your app doesn't need much load. If you're planning to serve a lot of ConcurrentUser with high RequestPerSecond I suggest to carefully plan the execution. I'm having trouble now. One of the projects I'm working on is using NodeJS acting as React SSR server (I know it's heavy). It crashes under pressure, with 10-ish CCU reaching only 12-RPS before crashing. The NodeJS server is not clustered yet though. If it is clustered, it might reach a bigger number, but I doubt it would be that significant. Scale up to 1000 users using Kubernetes and see yourself how big the compute bill next month. This is a fault in architecture and I'm telling you not to repeat my mistake. There are enhancements to NodeJS. NAPI is one, WASM is being introduced too, which is good news. You can utilize child_process and hire someone to write some fast binary for computation-heavy applications and execute that binary. Again, a lot of companies succeed with NodeJS. It's not to be completely avoided. Just be careful not to use it for something it is not used for.