web.config configuration best practice rules for making web pages fast and secure

Node.js is a server-side JavaScript environment that uses an asynchronous event-driven model. Node is built on top of Google’s V8 JavaScript engine. Google V8 actually compiles JavaScript into native machine code prior to execution, resulting in extremely fast runtime performance. Node enables you to rapidly build network apps that are lightning fast and highly concurrent.

Node.js and “event-driven” programming is best explained by this post using two analogies

Related Links:

1. Beginners Guide
2. Bad and Good Use cases for Node.js
3. Understanding node.js
4. Node.js for Java developers

A few Stack Overflow questions I found helpful:

1. Using Rails 3.1, where do you put your “page specific” javascript code?
2. Connecting Rails 3.1 with Multiple Databases
3. Adding HTML5 offline support to a Rails 3.1 app
4. Explain to me how config works in Rails
5. How can I start my Ruby environment from scratch? 
6. How do you access a Ruby on Rails Rails.root.join yml file from the console?
7. How can I programaticaly fill out a remote form with data from another form using Rails?
8. Load seed data in Rails 3 Project
9. What does a member and collection route mean?
10. Rails Namespace vs. Nested Resource
11. render partial object vs locals