Posted on by & filed under Content - Highlights and Reviews, Web Development.

JavaScript runs not only on the client, it can run on the server too using Node.js. Node.js is a platform that taps into the extremely fast V8 engine from Google using an evented I/O model. The winning feature is that a server in Node.js handles a single non-blocking thread with an event-loop. JavaScript, having an event-driven nature, is really well suited for this platform.

Try Node.js out to see how easily you can set up a server and serve content with server-side JavaScript. Below you’ll find a brief example where a server is listening on port 2222.

Try to replicate in Node.js all the functionalities you get with a standard server such as managing HTTP requests/responses, SSL support, access to database, logging, and so on. The approach Node.js follows for I/O activities is event-driven and non-blocking and, in this port 2222 scenario, programming in Node.js contains lots of callbacks to handle this asynchronous model.

Safari Books Online has the content you need

Take advantage of these Node.js resources in Safari Books Online:

Read What Is Node? to get up to speed on Node.js with this concise overview.
Node for Front-End Developers shows you how to use this popular JavaScript framework to create simple server applications, communicate with the client, build dynamic pages, work with data, and tackle other tasks.
In Sams Teach Yourself node.js in 24 Hours, expert web developer George Ornbo guides readers through every step of creating custom server-side solutions with Node.js.

About this author

Sebastiano Armeli-Battana is software engineer focused on JavaScript and Java development and he is really passionate about Web technologies. He works as consultant in SMS Management & Technology adopting Java technologies and he also works as Web freelancer. He is the author of a jQuery plugin called JAIL and he maintains his personal site at http://www.sebastianoarmelibattana.com.

Tags: Javascript, Node.js,

Trackbacks/Pingbacks

  1.  The State of JavaScript in 2012 « Sebastiano Armeli's Tech Blog