Answer:
Yes, Node.js is one-thread-per-process. This is a very deliberate design decision and eliminates the need to deal with locking semantics. If you don't agree with this, you probably don't yet realize just how insanely hard it is to debug multi-threaded code. For a deeper explanation of the Node.js process model and why it works this way (and why it will NEVER support multiple threads), read my other post.
| Previous Question | Next Question |
| Tell me what is the purpose of Node.js module.exports and how do you use it? | Tell me how to decide when to use Node.js? |