As with traditional web architectures, it's important to understand the why of using Node.js on the backend.
We've taken a look at the how of running Node.js, so now, let's take a look at how Node's client-server architecture differs from the traditional paradigm.
Traditional client-server architecture
To understand how Node.js differs from traditional architectures, let's look at the following request diagram:
In a traditional setup, each request (or connection) to the server spawns a new thread in memory on the server, taking up system random-access memory (RAM) until the number of possible threads is reached. After that, some requests must wait until more memory is available. If you're not familiar with the concept of threads, they're basically a small sequence of commands to run on a computer. What this multithreaded paradigm implies is that for each new request received...
