Tutorials

Node.js guide
Node tuts
Videos

Introduction to Node.js with Ryan Dahl
Node.js: Asynchronous Purity Leads to Faster Development
Parallel Programming with Node.js
Server-side JavaScript with Node, Connect & Express
Books

The Node Beginner Book
Mastering Node.js
Up and Running with Node.js
Node.js in Action
Blogs

Ryan Dahl's Node blog
How To Node
DailyJS
Nodejitsu blog
Podcasts

NodeUp
JavaScript resources

Crockford's videos (must see!)
Essential JavaScript Design Patterns For Beginners
JavaScript garden
JavaScript Patterns book
JavaScript: The Good Parts book
Node Modules

Wiki List on Github/Joyent/Node (start here last!)
Search for registered node.js modules

ruby on rails, node.js

Messenger.js is very flexible and can handle everything you need.

Supports Request / Reply Communication using round robin
Supports Publish / Subscribe (fanout) Communication
Supports Fire and Forget Communication
Supports middleware plugin for messenger Listeners (servers)
Extremely fast (disables TCP Nagle's algorithm)
Fault tolerant: clients will reconnect to servers even if server goes down and comes back later
Elegant API
Easily involves multiple servers

A terminal for your browser, using node/express/socket.io

a package manager for node

It’s worth pointing out that I am in no way affiliated with either language, and I certainly don’t think Node.js is completely a bad thing. Enabling people to code in more ways than before is always great, and I certainly respect the project. But, the people involved should be straight about the fact that their system is an approximation of what Erlang provides. It’s not “in some ways, a similar view.” Instead, it’s the same view, just executed in a different language that doesn’t support event-driven I/O natively.

On the 20th floor of a San Francisco skyscraper, a handful of developers are working on a new technology that’s changing the way real-time web apps are built and how they scale.
This technology, called Node.js, is being hailed as “the new Ruby on Rails” by some in the developer community. But it’s not a magic bullet, nor is it appropriate for all programming scenarios.

In the short time since its initial release in late 2009, Node.js has captured the interest of thousands of experienced developers, grown a package manager and a corpus of interesting modules and applications, and even spawned a number of startups.
What is it about this technology that makes it interesting to developers? And why has it succeeded while other server-side JavaScript implementations linger in obscurity or fail altogether?

The key factors are performance, timing, and focusing on a real problem that wasn't easily solved with other server-side dynamic languages.

Like myself, you might have read an article somewhere about Node.js or heard it mentioned a couple of times during some talk. So I actually got curious and decided to start learning more about it.

It’s the 10th blog post already in this series on Node.js! And for this post we’ll be talking about a fairly common scenario when developing applications with Node.js, namely reading data from one stream and sending it to another stream. Suppose we want to develop a simple web application that reads a particular file from disk and send it to the browser. The following code shows a very simple and naïve implementation in order to make this happen.