For the past 10 years, when back-end developers heard the words “JavaScript in the back end,” everyone instantly thought about Node.js.
Maybe not immediately at the start of those 10 years, but eventually it got to a point where the name was known to everyone as yet another available back-end technology based on JavaScript. And with its async I/O capabilities out of the box (because while other technologies also supported this, Node was the first one to have it as a core mechanic), it carved a portion of the market for itself.
More specifically, Node.js became almost the de facto choice for writing APIs, ...
