Downloaded 64 times
![Buffers
buffer.write('Hello Buffer');
buffer.toString('utf-8');
buffer[0] = 23;
buffer.slice(10, 20);](https://image.slidesharecdn.com/nodejs-should-ruby-developers-care-110218095101-phpapp02/75/Nodejs-Should-Ruby-Developers-Care-45-2048.jpg)
![Reverse Hello World
$ cat reverse_hello.js
var net = require('net');
net.createServer(function(socket) {
socket.on('data', function(buffer) {
console.log(buffer);
});
}).listen(0x27C3);
$ node reverse_hello.js &
[1] 3523
$ echo "hello world" | nc localhost 10179
<Buffer 68 65 6c 6c 6f 20 77 6f 72 6c 64 0a>](https://image.slidesharecdn.com/nodejs-should-ruby-developers-care-110218095101-phpapp02/75/Nodejs-Should-Ruby-Developers-Care-46-2048.jpg)
![Streams
stream.write(new Buffer([0x27, 0xC3]);
stream.pause();
stream.resume();
stream.destroy();](https://image.slidesharecdn.com/nodejs-should-ruby-developers-care-110218095101-phpapp02/75/Nodejs-Should-Ruby-Developers-Care-49-2048.jpg)
![Streams
$ cat echo.js
var net = require('net');
net.createServer(function(socket) {
socket.pipe(socket);
}).listen(0x27C3);
$ node echo.js &
[1] 6207
$ nc 127.0.0.1 10179
Hi, how are you?
Hi, how are you?](https://image.slidesharecdn.com/nodejs-should-ruby-developers-care-110218095101-phpapp02/75/Nodejs-Should-Ruby-Developers-Care-51-2048.jpg)
Uploaded byFelix Geisendörfer
Nodejs - Should Ruby Developers Care?
Node.js is a platform for building scalable network applications. It uses Google's V8 JavaScript engine and a non-blocking I/O model. Some key points: - Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, especially for real-time applications. - It has a large ecosystem of open source modules. Popular frameworks include Express and Fab. - While Node.js is very fast for I/O operations, memory usage can grow quickly and scaling to multiple cores requires multiple processes. - The author argues Node.js is suitable for single-page apps, real-time applications, and crawlers, but
More Related Content
Similar to Nodejs - Should Ruby Developers Care?
Nodejs - Should Ruby Developers Care?
- 1. Node.js Should ruby developerscare? 09.02.2011
- 2. About • FelixGeisendörfer • 23 years • Berlin, Germany
- 3. Core Contributor & Module Author node-mysql node-formidable
- 4. File uploading &processing as an infrastructure service for web & mobile applications.
- 5.
- 6. Node's goal isto provide an easy way to build scalable network programs.
- 7. Node.js • Created byRyan Dahl • Google’s V8 JavaScript engine (no DOM) • Module system, I/O bindings, Common Protocols
- 8. Installing $ git clone git://github.com/ry/node.git $ cd node $ ./configure $ make install
- 9. Hello World $ cattest.js console.log('Hello World'); $ node test.js Hello World
- 10. Ingredients libeio libev c-ares V8 http_parser
- 11. Philosophy • Just enoughcore-library to do I/O • Non-blocking • Close to the underlaying system calls
- 12.
- 13. Blocking I/O var a= db.query('SELECT A'); console.log('result a:', a); var b = db.query('SELECT B'); console.log('result b:', b); Time = SUM(A, B)
- 14. Non-Blocking I/O db.query('SELECT A',function(result) { console.log('result a:', result); }); db.query('SELECT B', function(result) { console.log('result b:', result); }); Time = MAX(A, B)
- 15. Non-Blocking I/O • Offloadmost things to the kernel and poll for changes (select, epoll, kqueue, etc.) • Thread pool for anything else
- 16. Why JavaScript? 3 Reasons
- 17. #1 - Thegood parts
- 18. V8 (Chrome) SpiderMonkey (Firefox) JavaScriptCore (Safari) #2 - JS Engine Wars Chakra (IE9) Carakan (Opera)
- 19. #3 - NoI/O in the core
- 20. What about eventmachine? • Can’t use blocking I/O libraries • No code sharing between client and server • Might be a valid choice if integrating with existing ruby code
- 21.
- 22. Frameworks • Express (popular) •Fab (revolutionary)
- 23. Rails still kicksnode’s ass in terms of productivity
- 24. Suitable Applications • Singe-pageapps • Real time • Crawlers
- 25. More Applications • Processmonitoring • File uploading • Streaming
- 26. What about allthose callbacks?
- 27. db.query('SELECT A', function(){ db.query('SELECT B', function() { db.query('SELECT C', function() { db.query('SELECT D', function() { // ouch }); }); }); });
- 29. You are holdingit wrong!
- 30. Nested Callbacks • Functiondoes too many things, break it up • Use an sequential abstraction library • Could be a sign that ruby is a better choice
- 31.
- 32.
- 33.
- 34. Ready for production? •0.4 to be released this month • API has settled down for most parts • Very few bugs, but YMMV
- 35.
- 36. Things that suck •Stack traces are lost at the event loop boundary • Utilizing multiple cores requires multiple processes • GC can be problematic
- 37.
- 38. Speed var http =require(’http’) var b = new Buffer(1024*1024); http.createServer(function (req, res) { res.writeHead(200); res.end(b); }).listen(8000); by Ryan Dahl
- 39. Speed 100 concurrent clients 1megabyte response node 822 req/sec nginx 708 thin 85 mongrel 4 (bigger is better) by Ryan Dahl
- 40. Speed • NGINX peakedat 4mb of memory • Node peaked at 60mb • Very special circumstances by Ryan Dahl
- 41. Questions? ✎ @felixge / [email protected]
- 42.
- 43.
- 44. Buffers • Raw Cmemory allocation • Similar to an array of integers • Can be converted to and from JS strings
- 45. Buffers buffer.write('Hello Buffer'); buffer.toString('utf-8'); buffer[0] =23; buffer.slice(10, 20);
- 46. Reverse Hello World $cat reverse_hello.js var net = require('net'); net.createServer(function(socket) { socket.on('data', function(buffer) { console.log(buffer); }); }).listen(0x27C3); $ node reverse_hello.js & [1] 3523 $ echo "hello world" | nc localhost 10179 <Buffer 68 65 6c 6c 6f 20 77 6f 72 6c 64 0a>
- 47.
- 48. “Streams are totime as arrays are to space.” -- Jed Schmidt @ JSConf.eu
- 49.
- 50. Streams stream .on('drain',function() {}) .on('data', function(buffer) {}) .on('end', function() {});
- 51. Streams $ cat echo.js varnet = require('net'); net.createServer(function(socket) { socket.pipe(socket); }).listen(0x27C3); $ node echo.js & [1] 6207 $ nc 127.0.0.1 10179 Hi, how are you? Hi, how are you?
- 52. Questions? ✎ @felixge / [email protected]