Scribd
Upload
179 views

Node JS

Node.js is a JavaScript runtime environment built on Google Chrome's V8 engine that runs JavaScript on the server side. It is designed for high concurrency without threads or processes using asynchronous and event-driven programming. This allows Node.js to handle a large number of concurrent connections efficiently. Node.js also uses the same JavaScript language on both the server-side and client-side.

Uploaded by

jesus jose
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
179 views

Node JS

Node.js is a JavaScript runtime environment built on Google Chrome's V8 engine that runs JavaScript on the server side. It is designed for high concurrency without threads or processes using asynchronous and event-driven programming. This allows Node.js to handle a large number of concurrent connections efficiently. Node.js also uses the same JavaScript language on both the server-side and client-side.

Uploaded by

jesus jose
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 9

A JavaScript runtime environment running

Google Chromes V8 engine


a.k.a. a server-side solution for JS
Compiles JS, making it really fast
Runs over the command line
Designed for high concurrency
Without threads or new processes
Never blocks, not even for I/O
Uses the CommonJS framework
Making it a little closer to a real OO language
Instead of threads Node uses an event loop
with a stack
Alleviates overhead of context switching
Threads Asynchronous Event-driven

Lock application / request with only one thread, which


listener-workers threads repeatedly fetches an event
Using incoming-request model Using queue and then processes
it
multithreaded server might manually saves state and then
block the request which might goes on to process the next
involve multiple events event
Using context switching no contention and no context
switches
Using multithreading Using asynchronous I/O
environments where listener facilities (callbacks, not
and workers threads are used poll/select or O_NONBLOCK)
frequently to take an incoming- environments
request lock
Request for index.html comes in
Stack unwinds and ev_loop goes to sleep
File loads from disk and is sent to the client
Servers do nothing but I/O
Scripts waiting on I/O requests degrades
performance
To avoid blocking, Node makes use of the
event driven nature of JS by attaching
callbacks to I/O requests
Scripts waiting on I/O waste no space
because they get popped off the stack when
their non-I/O related code finishes executing
Use of JS on both the client and server-side
should remove need to context switch
Client-side JS makes heavy use of the DOM, no
access to files/databases
Server-side JS deals mostly in files/databases, no
DOM
JSDom project for Node works for simple tasks, but not
much else
1. It's fast
2. It can handle tons of concurrent requests
3. It's written in JavaScript (which means you can
use the same code server side and client side)

Platform Number of request per


second
PHP ( via Apache) 3187,27
Static ( via Apache ) 2966,51
Node.js 5569,30
http://nodejs.org/
http://nodejs.org/cinco_de_node.pdf
http://ajaxian.com/archives/google-chrome-
chromium-and-v8
http://blog.chromium.org/2010/12/new-
crankshaft-for-v8.html
http://news.softpedia.com/news/IE9-RC-vs-
Chrome-10-9-vs-Opera-11-vs-Firefox-11-
Performance-Comparison-183973.shtml

You might also like