I see that some readers are mocking your analogy about NodeJs being the new Java but that has been case in my company. A few years ago we moved some backend pro

I see that some readers are mocking your analogy about NodeJs being the new Java but that has been case in my company. A few years ago we moved some backend projects from in house operated JavaEE application servers (Weblogic mostly) to cloud based micro services written in NodeJs and SpringBoot. NodeJs has been used for rapidly evolving projects with moving API and Springboot for slower paced projects with legacy SOAP API and lot of crypto. NodeJs apps are still very capable of communicating with message brokers, SQL/NoSQL databases, exposing REST, even SOAP API, doing some authentication, acting as message orchestrators, etc. Even though dealing with CPU bound tasks is not NodeJs forte. That being said I don't believe that replacing Java with NodeJs is a general trend in the enterprise world (but more than Golang).