This document provides an overview of a lunch and learn session about Node.js. It will discuss why Node.js may not be suitable for some tasks, describe key Node.js concepts like the event loop and asynchronous programming, and show examples of how Node.js has already been used within MDL frameworks like Seneca and groki-server. The session aims to explain Node.js keywords and what they mean, as well as what to expect, including an overview of the event loop and how to take advantage of multiple cores.
6. Node.js keywords
Developers nirvana
Single core
V8 JavaScript engine
Event based and Asynchronous/Non-blocking
7. Developers nirvana
It doesnt come by simply using JavaScript.
This reduces the barrier but It has to be
acquired.
Use the right tool for the right job
8. Single core
Threads are hard. Very very hard.
Take advantage of my 16 core box:
Multiple node js servers (one per core)
Fire up child processes
9. V8 JavaScript engine
Developed by Google and is open source
It's no longer a JavaScript "interpreter" as all
the modern engines do tons of JIT compiling
under the hood with interpretation only as a
fallback for execute-once code.
Microsoft forked nodejs for chakra as well.
10. Event based and Asynchronous/Non-blocking
NodeJS is bad ass manager
Give task to its subordinates and goes to sleep.
Wakes up only if new request comes in or its
subordinates complete the tasks.