node.js - Fast event based web application development


Published on

An introduction to node.js and the ecosystem around this great JavaScript engine

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

node.js - Fast event based web application development

  1. 1. node.js Fast event based web application development Wien, 7. April 2011 Gerhard Hipfinger
  2. 2. What is node.js? A JavaScript runtime Based on Googles V8 JavaScript engine High performance async event handling Module system, I/O system bindings, supports all common network protocols
  3. 3. Availability Available on all major platforms and on Windows too (via Cygwin or MinGW)
  4. 4. Module Management You want to use module management as there are many available! Over 1100 NPM is your friend curl | sh npm install express
  5. 5. Obligatory Hello, World! console.log('Hello, node.js World!'); > node hello.js Hello, node.js World! Create file hello.js with the content: Than type:
  6. 6. Design Goals Only a small core library Extensible module system Non blocking I/O As close to system calls as possible
  7. 7. Non Blocking I/O First we look at traditional blocking I/O I/O is serialized and the execution time is sum(opA, opB) var a = getSomethingFromDatabase(); c onsole.log(a); v ar b = getSomethingFromDatabase(); console.log(b);
  8. 8. Non Blocking I/O getSomethingFromDatabase(paramA, function(result) { console.log(result); }); getSomethingFromDatabase(paramB function(result) { console.log(result); }); Both queries are handled in an event queue and don't block each other Execution time is MAX(op1,op2)
  9. 9. Non Blocking I/O node.js uses epoll, kqueue or whatever is available at the underlying operating system So I/O does not waste your CPU cycles No busy waiting! Thread pool is used for everything else
  10. 10. (No) Threads The rest of your app is single threaded Easy programming model but is not useful for all kinds of apps
  11. 11. Your Webserver in 6 LOC var http = require('http'); http.createServer( function (req, res) { res.writeHead(200, {'Content-Type': 'text/plain'}); res.end('Hello Worldn'); }).listen(8888, ""); console.log('Server running at'); Pretty simple, isn't it?
  12. 12. Ever needed to poll for filechange? var fs = require('fs'); fs.watchFile(__filename, function() { console.log('I was changed!'); process.exit(0); });
  13. 13. So what can I do with node.js node.js is great for all I/O centric tasks Nearly all network apps are I/O centric (web or application server, socket server and so on)
  14. 14. node.js is good for... Web applications Streaming Unix tools (yeah, you can start your files with #!/usr/bin/node )
  15. 15. Don't use it for... CPU intense apps with few I/O Apps that need huge memory (V8 has a 1.9G limit) Multiple cores need multiple processes (single threaded)
  16. 16. Modules you will fall in love with Express Socket.IO Cradle (CouchDB module)
  17. 17. There is room for improvement Tool support Debugging Error reporting Windows support (when you realy want a Windows server) XML support
  18. 18. JavaScript Support Node JS contains CommonsJS EcmaScript5 Usable node API
  19. 19. Integration Great support for NonSQL stores: CouchDB, Redis But you still can use your RDB -> modules for all major databases
  20. 20. Resources You will need a good JavaScript understanding
  21. 21. Gerhard Hipfinger openForce Information Technology GesmbH Dresdner Str. 108 / 3. Stock / Top 11 1200 Wien TEL +43 1 3191775 FAX +43 1 3191775-20