As an asynchronous event driven JavaScript runtime, Node is designed to build scalable network applications. In the following 'hello world' example, many connections can be handled concurrently. Upon each connection the callback is fired, but if there is no work to be done, Node 64 bit will sleep.
This is in contrast to today's more common concurrency model where OS threads are employed. Thread-based networking is relatively inefficient and very difficult to use. Furthermore, users of Nodejs are free from worries of dead-locking the process, since there are no locks. Almost no function in the app directly performs I/O, so the process never blocks. Because nothing blocks, scalable systems are very reasonable to develop in Node.
Node.js is similar in design to, and influenced by, systems like Ruby's Event Machine or Python's Twisted. It takes the event model a bit further. It presents an event loop as a runtime construct instead of as a library. In other systems there is always a blocking call to start the event-loop. Typically behavior is defined through callbacks at the beginning of a script and at the end starts a server through a blocking call like EventMachine::run(). In Node js there is no such start-the-event-loop call. It simply enters the event loop after executing the input script. The tool exits the event loop when there are no more callbacks to perform. This behavior is like browser JavaScript — the event loop is hidden from the user.
HTTP is a first class citizen in Nodejs, designed with streaming and low latency in mind. This makes Node js well suited for the foundation of a web library or framework.
Just because Nodejs is designed without threads, doesn't mean you cannot take advantage of multiple cores in your environment. Child processes can be spawned by using child_process.fork() API, and are designed to be easy to communicate with. Built upon that same interface is the cluster module, which allows you to share sockets between processes to enable load balancing over your cores.