Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Here the author makes the follow statement:
Instead of spawning a new OS thread for each connection (and allocating the accompanying memory with it), each connection CREATES A PROCESS, which doesn’t require the memory block to go with it.
Does Node really spawn a process per request?! That’s not how I understood it… I thought node was a single threaded, single process? Sure you can load balance across a number of processes, but that’s not what he is claiming.
Thanks,
Ant
The article your linking is incorrect and has been removed by IBM.
Node.js is single threaded and runs in one process because JavaScript is single threaded.
Feel free to read Marak’s critique of said article