How NOT to write in Node.js
Download as PPTX, PDF13 likes17,061 views
This document discusses Node.js architecture and how software lives in hardware. It notes that Node.js uses a single-threaded, event loop model to avoid context switching and blocking I/O. This allows high throughput for operations like HTTP requests but is not optimal for long-running computations in a single thread. The document also addresses issues like callback hell and scaling event emitters, providing solutions like using promises and external queue systems. It concludes by stating Node.js is best for I/O operations, not all problems, and event loop models have existed in other frameworks before Node.js.
![ECMA-262 support
var arr = []
for(var i = 0, j = arr.length; i < j; ++i) {
var row = arr[i] // ufff…
}
var arr = []
arr.forEach(function(row) {
})](https://image.slidesharecdn.com/hownottowriteinnode-140207102715-phpapp01/85/How-NOT-to-write-in-Node-js-22-320.jpg)
![„Parallelism”
You can still fork another process
• threads_a_gogo
pool = require('threads_a_gogo').createPool(5)
pool.any.eval('myFunction( ... )')
• Fork process
var fork = require('child_process').fork;
var child = fork(__filename, [ 'arg1' ]);](https://image.slidesharecdn.com/hownottowriteinnode-140207102715-phpapp01/85/How-NOT-to-write-in-Node-js-29-320.jpg)
![Callback hell
Use async module:
async.series([
function(callback) {
],
function() {
operation1(callback)
},
})
function(callback) {
operationBloking()
return callback()
}
// all done...](https://image.slidesharecdn.com/hownottowriteinnode-140207102715-phpapp01/85/How-NOT-to-write-in-Node-js-36-320.jpg)
How NOT to write in Node.js
- 1. How NOT to write in Node.js Piotr Pelczar [email protected] PHPers, 6 Feb 2014
- 4. How software lives in hardware? • Operating systems are process based • Each process has assigned processor, registers, memory http://www.cs.uic.edu/~jbell/CourseNotes/OperatingSystems/4_Threads.html
- 5. How software lives in hardware? • Process paralelism using threads (thread pools) • Switching processor over processes/threads causes context switching http://www.cs.uic.edu/~jbell/CourseNotes/OperatingSystems/4_Threads.html
- 6. How software lives in hardware? 1. Avoid context switching = wasting time
- 7. How software lives in hardware? In trivial, sequential approach • Each operation is executed sequentially: O(t) > O(t+1) • if O(t) stucks, O(t+1) waits… http://cs.brown.edu/courses/cs196-5/f12/handouts/async.pdf
- 8. How software lives in hardware? This is cool, software flow is predictible But not in high throughput I/O
- 10. How software lives in hardware? High throughput I/O doesn’t mean: • Memory operations • Fast single-thread computing
- 11. How software lives in hardware? High throughput I/O means: • HTTP requests • Database connections • Queue system dispatching • HDD operations
- 12. Single-threaded, event loop model Problem: Imagine a man, who has a task: 1. Walk around 2. When bucket is full of water, just pour another bucket 3. Go to next bucket http://www.nightmare.com/medusa/async_sockets.html
- 13. Single-threaded, event loop model What is nonblocking I/O? Imagine a man, who has a task: 1. Walk around 2. When bucket is full of water, just pour another bucket 3. Go to next bucket http://www.nightmare.com/medusa/async_sockets.html
- 14. Single-threaded, event loop model Problem: Imagine a man, who has a task: 1. Walk around 2. When bucket is full of water, just pour another bucket, if not… continue 3. Go to next bucket http://www.nightmare.com/medusa/async_sockets.html
- 15. Single-threaded, event loop model How it is realised in low-level operating system? • select() • /dev/pool descriptors • kqueue • pool • epool
- 16. Single-threaded, event loop model How it is realised in low-level operating system? #include <sys/types.h> #include <sys/socket.h> int select(int nfds, fd_set *readfds, fd_set *writefds, fd_set *exceptfds, const struct timeval *timeout);
- 17. Single-threaded, event loop model 2. Avoid I/O blocking
- 19. Node.js architecture JavaScript C/C++ Node std library node bindings (socket, http, …) Google V8 Thread Pool (libeio) Event loop (libev)
- 20. Node.js architecture • Single-threaded no context switching • Event loop no waits • Javascript (Google V8) • ECMA-262 support
- 22. ECMA-262 support var arr = [] for(var i = 0, j = arr.length; i < j; ++i) { var row = arr[i] // ufff… } var arr = [] arr.forEach(function(row) { })
- 24. Node.js architecture • Everything runs in parallel except your code • When currently code is running, (not waiting for I/O descriptors) whole event loop is blocked
- 25. „Parallelism” • Let’s compute Fibonacci function fib(n) { return (n < 2) ? 1 : (fib(n-2)+fib(n-1)); } This will simply block main (single) thread.
- 26. „Parallelism” • How about process.nextTick() ?
- 27. „Parallelism” • … but next iteration over function is delayed into next event loop iteration • That means each descriptor is checked before computation.
- 28. „Parallelism” process.nextTick() to speed up computations is a myth Node.js is not good solution to make single-process computations
- 29. „Parallelism” You can still fork another process • threads_a_gogo pool = require('threads_a_gogo').createPool(5) pool.any.eval('myFunction( ... )') • Fork process var fork = require('child_process').fork; var child = fork(__filename, [ 'arg1' ]);
- 30. Callback hell is a myth we can deal with it
- 31. Callback hell • Language construction – callback function • When operation is ready, call function passed as an argument someOperation(arg1, arg2, function() { console.log('cool!'); })
- 32. Callback hell • When many operations are ready…
- 33. var amqp = require('amqp'); var connection = amqp.createConnection(); connection.on('ready', function() { connection.exchange("ex1", function(exchange) { connection.queue('queue1', function(q) { q.bind(exchange, 'r1'); q.subscribe(function(json, headers, info, m) { console.log("msg: " + JSON.stringify(json)); }); }); }); }); This is callback hell
- 34. Callback hell Deal with callback hell in many ways: • Define callbacks as local variables • Use async module • Use PROMISE design pattern
- 35. Callback hell Define callbacks as local variables, like this: var whenSthElseDone = function() { // done... } var whenSthDone = function() { operation(whenSthElseDone) } operation(whenSthDone)
- 36. Callback hell Use async module: async.series([ function(callback) { ], function() { operation1(callback) }, }) function(callback) { operationBloking() return callback() } // all done...
- 37. Callback hell PROMISE design pattern: var Promise = require('promise'); var promise = new Promise(function (resolve, reject) { operation1(function (err, res) { if (err) reject(err); else resolve(res); }); });
- 38. Callback hell PROMISE design pattern: promise.then(function(res) { // done... })
- 39. Events (event bus) Triggering event does’t block whole event loop is a myth
- 40. Events var eventbus = require('events').EventEmitter myFunction() { operation1(function() { eventbus.emit('myFunctionIsDone', { result: 1234 }) } }
- 41. Events var eventbus = require('events').EventEmitter eventbus.on('myFunctionIsDone', function(data) { console.log('cool! ') }) Trigger waits until all listeners are done. So do not make long-running operations in event subscribers.
- 42. Scaling EventEmitter Triggering events in event bus via EventEmitter does not scale!
- 43. Scaling EventEmitter • Triggering events in event bus via EventEmitter does not scale! • Events are visible locally in main thread
- 44. Scaling EventEmitter We need to use external queue system to touch distributed nodes (3rd party for our application written in Node.js)
- 45. Scaling EventEmitter RabbitMQ is cool because: • based on AMQP protocol (so integrates 3rd party software – an abstraction) • Queue async system • Publish-subscribe async model • Request-Response model
- 46. Scaling EventEmitter Emit: 1. Trigger event in your application via EventEmitter 2. Catch it locally 3. Re-trigger via RabbitMQ
- 47. Scaling EventEmitter Receive: 1. Subscribe on RabbitMQ exchange 2. Trigger local event in application
- 48. Scaling EventEmitter This is only to separate responsibilities and good design of application
- 49. Not only Node.js Node.js is not a religion! It is only an implementation of async programming model
- 50. Not only Node.js Node.js is not a religion. Last time - hype. It only utilizes event-loop model, known from a long time… • GUI frameworks • Tornado – Python • Linkedin parseq – Java • Async and Await – C# • Cramp – Ruby • reactphp – PHP, ehhh… WAT?!
- 51. Event loop, single-threaded model is not solution for all your problems… Especially for long-running computings in single thread. It’s good for high throughput I/O.