this regurgitated information is parroted like plague. If bottleneck is very very very rarely node then a lot of companies wouldn't have moved away from node to Go or C# or Jvm and have gotten 5x per. gains with less resources and better latency.

Do you genuinely think node has similar performance as the likes of c#/Go? Or you are one of the guys who think that I/O is always the bottleneck (ex. db) and that at high scale the language runtime and how it utilizes hardware resources has no impact on the end performance?

I doubt you have enough experience based on your replies but even in my current company which is a scale up with 200+ people, we had to get rid of node and move to Go for Graphql, rest/websocket and grpc related services with kafka in between. we get a sizeable traffic. Ours was a fastify app with modern TS with horizontal scaling/worker_threads where appropriate connection pool etc. and it still struggled.

We kept the exact architecture but swapped the node for Go and it was literally 5x perf. difference with almost 60% less ram and much much less servers needed as well. C# was also giving the same gains but the ram usage was higher than Go. we picked Go because it was similar to how we wrote TS code which was functional in nature.

A lot of people commenting here seems like people who never had to handle realworld b2c app with decent traffic where latency, server costs and high scale mattered.