Node.jsShael Joon & Matt Simonis

Background

• Server Side JavaScript

• Developed by Ryan Dhal (2009)

• Currently owned by Joyent

• Based off Google’s V8 JavaScript Engine (which is written in C and C++)

• Open Source

It’s Asynchronous

• Non-blocking due to system event notifications

• Not having to deal with common multithreading problems such as deadlocks, resource sharing and etc. (See [6] for more details)

• Scalability (930k[tested] to 1500k[claimed] connections) [4]

• Most of the server and client side work can be done in JavaScript

Usage domain areas/users

MicrosoftNode gives Azure users the first end-to-end JavaScript experience for the development of a whole new class of real-time applications.

eBayNode’s evented I/O model freed us from worrying about locking and concurrency issues that are common with multithreaded async I/O.

Linkedin

On the server side, our entire mobile software stack is completely built in Node. One reason was scale. The second is Node showed us huge performance gains.

Yahoo

Node.js is the execution core of Manhattan. Allowing developers to build one code base using one language – that is the nirvana for developers.

http://nodejs.org/

Google Trends – “node.js”

http://www.google.com/trends/?q=node.js

Ample Resources

• Free e-Books

• Code Samples including 3rd party sources

• Modules usage guides/samples

• Benchmarking and comparisons to other technologies

• However, it is missing scholarly papers and research.

Modules

• Modules are plugins/add-ons/extensions for Node to help with development process.

• Often code examples are included alongside the module.

• Several categories of modules.

• Modules are plugins/add-ons/extensions for Node to help with development process.

3000+ modules in the areas below•Web frameworks

• Routers

• Static file servers

• Microframeworks

• Frameworks

• Middleware

• JSGI

• Connect

• Other middleware

• Other

• Database

• MS SQL Server

• PostgreSQL

• MySQL

• SQLite

• Oracle

• NoSQL and Key/Value

• Mongo

• Hive

• Redis

• CouchDB

• Templating

• CSS Engines

• Content Management Systems

• Build and Deployment

• Package Management Systems

• Module Loader

• OpenSSL / Crypto / Hashing

• SMTP

• TCP / IP

• Multiple protocols

• HTTP

• FTP

• E-mail

• XMPP

• Other networking

• RPC

•Web Sockets & Ajax

• Message Queues

• Class systems

• Testing / Spec Frameworks

•Wrappers

• Parsers

• JSON

• XML

• Command Line Option Parsers

• Parser Generators

• Other Parsers

• Debugging / Console Utilities

• Compression

• Graphics

• Sound

• Payment Gateways

• API clients

• Control flow / Async goodies

• I18n and L10n modules

• Boilerplates

• Continuous Integration Tools

• DDD, CQRS, EventSourcing

• Desktop application related

• JavaScript threads

• Other

https://github.com/joyent/node/wiki/modules

Benchmarks [1]

Benchmarks [1]

Benchmarks [1]

Benchmarks [1]

Benchmarks [1 , 4 ]• Analysis

• Conducted by the owner of Erwin

• Comparison of all event based languages

• Tested on a single core

• Recognized by Tom Hughes-Croucher (representing Node)

• Node is fairly new and yet it can compete with other mature technologies

• Performance is not everything. Other factors (Usability, stability, etc) should be considered as well.

• THEY ARE ALL AVERAGES BEING PLOTTED. Concern about exceptional cases (unusually long calls) may bring down the overall performance down.

Benchmarks [2]

Benchmarks

Analysis

• Conducted by 3rd party

• Comparing Node against Apache + PHP is an unfair experiment but is a realistic case.

• Benchmarking tool was sharing resources while the tests were run.

Benchmarks[5]

Benchmarks

Analysis

• Conducted by 3rd party

• Heavier work loads being tested – DB access was involved.

• Run on a single machine and was not distributed.

Benchmarks [3]

Analysis

• Conducted by 3rd party

• Simple random number generation / return test.

• Missing physical hardware set information.

Benchmarks – Final thoughts

• Node is worth investigating as it shows rapid growth in 3 years of existence.

• Needs higher quality benchmarking tests conducted in real life scenarios.

• Scholarly research is still scarce.

• Recommended domain areas – scalable web services, non critical software.

Usage [4]

Chat server – client may connect via telnet [4]

SourcesWeb Posts:

[1] Ostinelli , Roberto. "A comparison between Misultin, Mochiweb, Cowboy, NodeJS and Tornadoweb."www.ostinelli.net. Oostinelli, May 2011. Web. 19 Mar 2012. <http://www.ostinelli.net/a-comparison-between-misultin-mochiweb-cowboy-nodejs-and-tornadoweb/>.

[2] Zgadzaj, Maciej. "Benchmarking Node.js - basic performance tests against Apache PHP."http://zgadzaj.com. N.p., August 19, 2010. Web. 19 Mar 2012. <http://zgadzaj.com/benchmarking-nodejs-basic-performance-tests-against-apache-php>.

 [3] B, K. "Benchmarking nodejs : comparing nodejs and tomcat - random generator." http://fl-ex.blogspot.com. N.p., 13 December 2011. Web. 19 Mar 2012. <http://fl-ex.blogspot.com/2011/12/comparing-random-generator-nodejs-and.html>.

  [4] Hughes-Croucher, Tom, dir. Tech Talk: Tom Hughes-Croucher (Joyent) — “Node.js at Scale”. Joyent, 2011. Web. 19 Mar 2012. <http://sna-projects.com/blog/2011/08/nodejs/>. <http://sna-projects.com/blog/2011/08/nodejs/>.

[5] SUBBU, ALLAMARAJU. "Nodejs vs Play for Front-End Apps." subbu.org. N.p., MARCH 26, 2011. Web. 19 Mar 2012. <http://www.subbu.org/blog/2011/03/nodejs-vs-play-for-front-end-apps>.

IEEE Paper:

[6] Tilkov, S.; Vinoski, S.; , "Node.js: Using JavaScript to Build High-Performance Network Programs," Internet Computing, IEEE , vol.14, no.6, pp.80-83, Nov.-Dec. 2010

doi: 10.1109/MIC.2010.145

URL: http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=5617064&isnumber=5617049

Why Node.js?

Why Node.js?

• Fast and scalable

• Transferrable knowledge

Why Node.js?

• Fast and scalable

• Transferrable knowledge

• Event driven with non-blocking I/O

Why Node.js?

• Fast and scalable

• Transferrable knowledge

• Event driven with non-blocking I/O

• Hundreds of modules

Modules

Modules

http

Express

Socket.io

mongoose

ejsJade

node-imap

node-ftpnode.bcrypt.js

node-crypto

Modules Used

Modules Used

• Express

• bcrypt

• mongoose

• Socket.io

• child_process

Express

var app = express.createServer();

app.get('/', function(req, res){ res.send('Hello World');});

app.listen(3000);

Express & RESTapp.get('/user/playlist', function(req, res) { if (req.session.user) { Playlist.findOne({userid: req.session.user._id}, function(err, playlist) { if (playlist) { res.json(playlist.songs); } else { res.redirect('/404'); } }); } else { res.redirect('/404'); }});

Express & RESTapp.post('/register', function(req, res) { var newUser = new User(); newUser.username = req.body.username; newUser.password = req.body.password; newUser.display_name = req.body.displayname; newUser.date_created = new Date(); newUser.save(function(err) { if (err) { res.redirect('error'); } else { res.redirect('home'); } });});

Mongoose

var UserSchema = new Schema({ username: { type: String, index: { unique: true } }, password: String, salt: String, display_name: String date_created: Date});

var User = mongoose.model('User', UserSchema);

socket.io

socket.on('disconnect', function() { if (socket.handshake.session.user) { var user = socket.handshake.session.user.username; io.sockets.in(user).emit('exit', { user: user }); }});

YouTube API

YouTube API

• Very well documented

• Tons of information available from player

• Easy to integrate

Problems

Problems

• mongoose schemas

• Socket.io access to sessions

• Handling groups of sockets

• Passing server-side data to front-end

• YouTube API and HTML5

What I Learned

What I Learned

• Easy to get an app up and running

• MongoDB is incredibly simple

• YouTube API is great to work with

ContactMatt Simonis

Rochester Institute of Technology

website: www.mattsimonis.com

email: matts12290@gmail.com

twitter: @mattsimonis

Shael Joon

Rochester Institute of Technology

website: www.shaeljoon.com

email: shaeljoon@gmail.com