While this is a hotly debated topic (and I've been in more than enough debates about it)... you, my good sir/ma'am... have hit the nail on the head.
Node.JS is perfectly fine, if you only run in one CPU core and if you don't need Inter-Process Communication (IPC). That is, if you're in the perfect nirvana world of microservices.
For everyone else, the Event Driven design of Node.JS probably causes more harm than good. The difficulty for everyone not using Node.JS, is that orchestration & synchronisation is a challenge - though, tools exist no matter what language you're writing in (including the times I have to write a cronjob that works in zsh, etc).
FWIW, most of my work is in Java, and thanks to native compilation in something like Graal, we can now produce smaller Docker images & use less memory than other teams of ours that use Node.JS (and our build pipelines are ~15x quicker, thanks mostly to TypeScript compilation).
Everything has trade-offs somewhere, and that isn't limited to IT work.
While this is a hotly debated topic (and I've been in more than enough debates about it)... you, my good sir/ma'am... have hit the nail on the head.
Node.JS is perfectly fine, if you only run in one CPU core and if you don't need Inter-Process Communication (IPC). That is, if you're in the perfect nirvana world of microservices.
For everyone else, the Event Driven design of Node.JS probably causes more harm than good. The difficulty for everyone not using Node.JS, is that orchestration & synchronisation is a challenge - though, tools exist no matter what language you're writing in (including the times I have to write a cronjob that works in zsh, etc).
FWIW, most of my work is in Java, and thanks to native compilation in something like Graal, we can now produce smaller Docker images & use less memory than other teams of ours that use Node.JS (and our build pipelines are ~15x quicker, thanks mostly to TypeScript compilation).
Everything has trade-offs somewhere, and that isn't limited to IT work.
Thank you..
Very true.