Node.js and How JavaScript is Changing Server Programming
28 likes10,508 views
The document presents an overview of server-side JavaScript (SSJS) and introduces Node.js, emphasizing its efficiency through non-blocking and event-driven architecture. It highlights the advantages of using JavaScript for server programming, such as code reuse and progressive enhancement, and showcases basic Node.js server code examples. Additionally, it discusses the Node.js ecosystem and the importance of libraries like Mustache.js for rendering HTML.
Node.js and How JavaScript is Changing Server Programming
- 1. Node.js How JavaScript is Changing Server Programming Tom Hughes-Croucher @sh1mmer
- 2. This is how we roll 1. Server-Side JavaScript Overview 2. Introduction to Node.js 3. The Node.js ecosystem 4. Getting started
- 3. Server Side Javascript IS SO AWESOME MY ENTIRE PRESENTATION IS IN COMIC SANS AND YOU WILL STILL LOVE ME AT THE END
- 4. Why SSJS?
- 5. JavaScript programmers 3>2>1
- 6. Massive Code base of YUI and other JS libraries I heard some people use this thing called jQuery, but I’m not convinced it’ll catch on
- 7. Laziness or “I’m sick of writing stuff twice” I could have said efficiency, but I think we all secretly long to lounge around in our y-fronts.
- 8. Progressive Enhancement is free* Remember WWCD (What Would Crockford Do) *close enough
- 9. TL;DR: SSJS is Awesome Like a Unicorn riding a Narwhal
- 11. Why now?
- 14. “Yahoo!'s corporate motto is: Don't be eval().“
- 15. “Doug Crockford's JavaScript is so strict, that uncaught exceptions would trigger global thermonuclear war“
- 16. 2. JavaScript Runtimes
- 17. Runtimes • V8 (Google), C++ • Spider Monkey (Mozilla), C++ • Rhino (Mozilla), Java • JavaScript Core (Apple), C++
- 18. V8 Spider Monkey JavaScript Performance
- 19. Node.js • Server-side JavaScript process • Uses V8 • Non-blocking • Event Driven • CommonJS module format
- 20. AW Node.js • ESServer-side JavaScript process OM • Uses V8 • Non-blocking • • Event Driven CommonJS module format E!
- 21. Node is ⎻⎻⎻⎻⎻ this fast
- 22. concurrency=300, Smaller is Better 400 300 response time (ms) server nginx 200 thin tornado node_buffer 100 24 26 28 210 212 214 216 218 response size (bytes)
- 24. Why non-blocking matters
- 25. var result = db.query("select * from T"); // use result
- 26. What are we waiting for?
- 27. Event Loop vs. Threads
- 28. Apache vs NGINX concurrency × reqs/sec http://blog.webfaction.com/a-little-holiday-present
- 29. Apache vs NGINX concurrency × memory http://blog.webfaction.com/a-little-holiday-present
- 30. Node Basics
- 31. var http = require('http'); http.createServer(function (req, res) { res.writeHead(200, {'Content-Type': 'text/plain'}); res.end('Hello Worldn'); }).listen(8124, "127.0.0.1"); console.log('Server running at http://127.0.0.1:8124/');
- 32. var http = require('http'); //include the http library
- 33. http.createServer(function (req, res) { }).listen(8124, "127.0.0.1"); //create an http server //when ‘stuff’ happens call this anonymous function //listen on port 8124 of the IP 127.0.0.1
- 34. http.createServer(function (req, res) { res.writeHead(200, {'Content-Type': 'text/plain'}); res.end('Hello Worldn'); }) //when ‘stuff’ happens my function fires //I get a request object and a response object //I write to the response object header //HTTP status 200 and content-type ‘text/plain’ //close the response with the body: //Hello World
- 35. console.log('Server running at http://127.0.0.1:8124/'); //write Server is running at http://127.0.0.1:8124/ //to the console
- 36. Node Ecosystem
- 49. NPM is written in JavaScript!
- 50. // kludge until this is normal. if (!process.EventEmitter.prototype.on) { process.EventEmitter.prototype.on = process.EventEmitter.prototype.addListener } var path = require("path") if (!process.execPath) { process.execPath = path.join(process.installPrefix, "bin", "node") } var npm = exports , set = require("./lib/utils/set") , get = require("./lib/utils/get") , ini = require("./lib/utils/ini") , log = require("./lib/utils/log") , fs = require("fs") npm.commands = {} npm.SHOULD_EXIT = true try { var j = JSON.parse(fs.readFileSync(path.join(__dirname, "package.json"))+"") npm.version = j.version } catch (ex) { log(ex, "error reading version") npm.version = ex }
- 52. Which libraries to use?
- 53. Mustache.js
- 55. var view = { title: "Joe", calc: function() { return 2 + 4; } } var template = "{{title}} spends {{calc}}"; var html = Mustache.to_html(template, view);
- 56. node-paperboy
- 60. DOM+YUI3
- 62. Multi-core Node.js Node+Web Workers
- 63. Master var sys = require('sys'); var Worker = require('webworker').Worker; var w = new Worker('foo.js'); w.onmessage = function(e) { sys.debug('Received mesage: ' + sys.inspect(e)); w.terminate(); }; w.postMessage({ foo : 'bar' }); Worker onmessage = function(e) { postMessage({ test : 'this is a test' }); }; onclose = function() { sys.debug('Worker shuttting down.'); };
- 64. Summary • SSJS is awesome because • We are JavaScript programmers • Reuse (libraries/code) • Progressive Enhancement • Node.js + YUI3 rocks • YUI 3’s was easy to get running on Node.js • Server side DOM allows for a single code base
- 65. Today presentation was Brought to you by And the fonts: the letters: Comic Sans J and S monofur Tom Hughes-Croucher Slides, etc --> http:// @sh1mmer speakerrate.com/sh1mmer croucher@yahoo-inc.com Pls rate me. kthxbai.