Nodejs

1,797 views

Published on

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,797
On SlideShare
0
From Embeds
0
Number of Embeds
64
Actions
Shares
0
Downloads
19
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Nodejs

  1. 1.    Kishore Yekkanti Thoughtworks Ryan Dahl
  2. 2.    What ?
  3. 3.    Why ?
  4. 4.    I/O needs to be done differently var  result  = db.query(”select * from T”); // use result What is software doing while it queries the database
  5. 5.    db.query("select..", function (result) {        // use result });
  6. 6.    100 concurrent clients 1 MB response  node       822  req/sec  nginx     708  thin        85  mongrel  4
  7. 7.    Ingredients
  8. 8.    Who ?
  9. 9.    Design Goals  No function should directly peform I/O.  To receive info from disk, network or another  process there must be a callback.  Stream every thing, never force buffering of data.  Have built in support for the most important  protocols (TCP, DNS, HTTP).  Chunked requests and responses  Keep – alive  Should be familiar to client­side JS programmers  and old school UNIX hackers.
  10. 10.    How ?
  11. 11.    Install $ git clone git://github.com/ry/node.git $ cd node $ ./configure $ make install
  12. 12.    Enough Is Enough !!
  13. 13.    Quake Stats Quake Server (hosted through sinatra). Node serverNode Client (Browser) Faye (websocket server) Node-static (to server static pages)
  14. 14.    kishoreyekkantikishoreyekkanti kishoreyekkanti.blogspot.com Questions ?

×