Why should I get started with Node.js? - rain
« Home / All Guides Now that you're all hyped up about using node.js, it's time to convince your boss. Well, maybe. I have had the pleasure of consulting for different businesses on whether node.js is the right technology, and sometimes the answer is simply no. So this guide is my opinionated collection of advice for those of you that want to explore whether node.js makes sense for their business, and if so, how to convince the management. Felix's Node.js Convincing the boss guide Felix's Node.js Convincing the boss guide
Node.js PaaS: Nodejitsu (part 1 of 3) - startups & node.js
Max Ogden Blogotronz Max Ogden Blogotronz Description of and notes on the node.js Stream API There is also a screencast version of this article. node bills itself as JavaScript evented I/O. In a nutshell that means if you are trying to solve a problem that is I/O bound (the limiting factor is reading/writing to relatively slow interfaces) then node can provide some useful abstractions to you. An example is if you are writing an application that has to talk to multiple databases, a caching layer, a load balancer, external web services, mobile clients, third party auth providers and serve web applications then node acts as a nice glue between all of the things.
Posted on 29 September 2010 I was lucky enough to have a short chat with Ryan at JSConf.eu last weekend in Berlin about the memory allocation comparison between Node.js and RingoJS I had done. He didn’t have any suggestion for tuning Node.js or V8 for higher memory and garbage collector throughput, but thought it was possible that Node’s lackluster performance in the benchmark had to do with binary buffers and getting data in and out of them. Thinking about a memory and garbage collection benchmark that didn’t involve buffers quickly led me to JSON. Update on my Node.js Memory and GC Benchmark - Hannes Wallnöfer Update on my Node.js Memory and GC Benchmark - Hannes Wallnöfer
Recently I have been looking around the internet for various info about Node.js. At first, my intent was to make some sort of infographic on the topic, but later I have changed my mind. I like infographics a lot, but they have an important limitation - their links aren't clickable. That is why I have decided to simply categorize the information and share it. Hopefully, someone will benefit from that. In case you think that something has to be added or changed, please, share it in the comments below. My Node.js Linksheet - Progstr Filer My Node.js Linksheet - Progstr Filer
Staying up with Node.JS To many beginner Node.JS users, a fundamental and immediate apparent disadvantage of writing their web applications with Node.JS lies in the inability to save a file, refresh the browser and see their changes live. This “problem” is rooted of course in significantly different architectures. In the case of, for example, PHP applications we traditionally separate the role of the web server and request handler. The monolithic web server maps incoming requests to the execution of particular files in the file system, which become our handlers. In most setups, the web server is mostly limited to inspecting two pieces of a HTTP request: the resource (like /test.php) and the Host header (like www.mydomain.com) for virtual hosts (vhosts) support. GET /test.php HTTP/1.1Host: www.mydomain.com Staying up with Node.JS
Articles/Etc | node.js

Plugins/Modules/Etc | node.js

Programs | node.js

Tutorials/Guides/Etc | node.js

NodeUp | A Node.js Podcast
Nodebits - Bits of inspiration to keep the node spirit alive
Getting into Node | On the JVM Updated 2011-04-27: forgot to add Backbone.js Most of the net is abuzz about Node , so it’s hard to miss it. I’ve been sitting on the sidelines for several months now, but after attending a TechTalksTO talk on Node given by James Duncan of Joyent, I’m convinced I should dive in. tl;dr version Getting into Node | On the JVM
joyent/node - GitHub