45
Rami Sayar - @ramisayar Technical Evangelist Microsoft Canada

Node.js 101

  • Upload
    fitc

  • View
    716

  • Download
    0

Embed Size (px)

DESCRIPTION

Node.js 101 with Rami Sayar Presented on September 18 2014 at FITC's Web Unleashed Toronto 2014 Conference More info at www.fitc.ca OVERVIEW Node.js is a runtime environment and library for running JavaScript applications outside the browser. Node.js is mostly used to run real-time server applications and shines through its performance using non-blocking I/O and asynchronous events. This talk will introduce you to Node.js by showcasing the environment and its two most popular libraries: express and socket.io. TARGET AUDIENCE Beginner web developers ASSUMED AUDIENCE KNOWLEDGE Working knowledge of JavaScript and HTML5. OBJECTIVE Learn how to build a chat engine using Node.js and WebSockets. FIVE THINGS AUDIENCE MEMBERS WILL LEARN Node.js environment and basics Node Package Manager overview Web Framework, express, basics WebSockets and Socket.io basics Building a chat engine using Node.js

Citation preview

Page 1: Node.js 101

Rami Sayar - @ramisayar

Technical Evangelist

Microsoft Canada

Page 2: Node.js 101

• Node.js Basics and Environment

• Node Package Manager Overview

• Web Framework Express Basics

• WebSockets and Socket.io basics

• Building a Chatroom using Node.js

Page 3: Node.js 101

• Working knowledge of JavaScript and HTML5.

Note: Slides will be made available.

Page 4: Node.js 101
Page 5: Node.js 101
Page 6: Node.js 101
Page 7: Node.js 101
Page 8: Node.js 101
Page 9: Node.js 101
Page 10: Node.js 101

• It was created by Ryan Dahl in 2009.

• Still considered in beta phase.

• Latest version is v0.10.31.

• Open-source!

• Supports Windows, Linux, Mac OSX

Page 11: Node.js 101

Node.js is a runtime environment and library for running JavaScript applications outside the browser.

Node.js is mostly used to run real-time server applications and shines through its performance using non-blocking I/O and

asynchronous events.

Page 12: Node.js 101

• Node is great for streaming or event-based real-time applications like:• Chat Applications• Dashboards• Game Servers• Ad Servers• Streaming Servers• Online games, collaboration tools or anything meant to be real-time.

• Node is great for when you need high levels of concurrency but little dedicated CPU time.

• Great for writing JavaScript code everywhere!

Page 13: Node.js 101

• Microsoft

• Yahoo!

• LinkedIn

• eBay

• Dow Jones

• Cloud9

• The New York Times, etc…

Page 14: Node.js 101

• Five years after its debut, Node is the third most popular project on GitHub.

• Over 2 million downloads per month.

• Over 20 million downloads of v0.10x.

• Over 81,000 modules on npm.

• Over 475 meetups worldwide talking about Node.

Reference: http://strongloop.com/node-js/infographic/

Page 15: Node.js 101

aka.ms/node-101

Page 16: Node.js 101
Page 17: Node.js 101
Page 18: Node.js 101

“A programming paradigm in which the flow of the program is determined by events such as user actions (mouse clicks, key

presses) or messages from other programs.” – Wikipedia

Page 19: Node.js 101

• Node provides the event loop as part of the language.

• With Node, there is no call to start the loop.

• The loop starts and doesn’t end until the last callback is complete.

• Event loop is run under a single thread therefore sleep() makes everything halt.

Page 20: Node.js 101

var fs = require('fs');

var contents = fs.readFileSync('package.json').toString();console.log(contents);

Page 21: Node.js 101

var fs = require('fs');

fs.readFile('package.json', function (err, buf) {console.log(buf.toString());

});

Page 22: Node.js 101

• Event loops result in callback-style programming where you break apart a program into its underlying data flow.

• In other words, you end up splitting your program into smaller and smaller chunks until each chuck is mapped to operation with data.

• Why? So that you don’t freeze the event loop on long-running operations (such as disk or network I/O).

Page 23: Node.js 101

http://callbackhell.com/

Page 24: Node.js 101

• A function will return a promise for an object in the future.

• Promises can be chained together.

• Simplify programming of async systems.

Read More: http://spin.atomicobject.com/2012/03/14/nodejs-and-asynchronous-programming-with-promises/

Page 25: Node.js 101

step1(function (value1) {step2(value1, function (value2) {

step3(value2, function (value3) {step4(value3, function (value4) {

// Do something with value4});

});});

});

Q.fcall(promisedStep1).then(promisedStep2).then(promisedStep3).then(promisedStep4).then(function (value4) {

// Do something with value4}) .catch(function (error) {

// Handle any error from all above steps}).done();

Page 26: Node.js 101

• James Coglan – “Callbacks are imperative, promises are functional: Node’s biggest missed opportunity”• https://blog.jcoglan.com/2013/03/30/callbacks-are-

imperative-promises-are-functional-nodes-biggest-missed-opportunity/

Page 27: Node.js 101
Page 28: Node.js 101

• Allows you to listen for “events” and assign functions to run when events occur.

• Each emitter can emit different types of events.

• The “error” event is special.

• Read More: http://code.tutsplus.com/tutorials/using-nodes-event-module--net-35941

Page 29: Node.js 101

• Streams represent data streams such as I/O.

• Streams can be piped together like in Unix.

var fs = require("fs");// Read Filefs.createReadStream("package.json")

// Write File.pipe(fs.createWriteStream("out.json"));

Page 30: Node.js 101

• Node.js has a simple module and dependencies loading system.

• Unix philosophy -> Node philosophy• Write programs that do one thing and do it well -> Write modules that

do one thing and do it well.

Page 31: Node.js 101

• Call the function “require” with the path of the file or directory containing the module you would like to load.

• Returns a variable containing all the exported functions.

var fs = require("fs");

Page 32: Node.js 101

• Official package manager for Node.

• Bundled and installed automatically with the environment.

Frequent Usage:

• npm install --save package_name

• npm update

Page 33: Node.js 101

{"name": "Node101","version": "0.1.0","description": "FITC Node101 Presentation Code","main": "1_hello_world.js","author": {"name": "Rami Sayar","email": ""

}} http://browsenpm.org/package.json

Page 35: Node.js 101

• Reads package.json

• Installs the dependencies in the local node_modules folder

• In global mode, it makes a node module accessible to all.

• Can install from a folder, tarball, web, etc…

• Can specify dev or optional dependencies.

Page 36: Node.js 101

Async is a utility module which provides straight-forward, powerful functions for working with asynchronous JavaScript.

async.map(['file1','file2','file3'], fs.stat, function (err, results) {

// results is now an array of stats for each file

});

async.filter(['file1','file2','file3'], fs.exists, function (results) {

// results now equals an array of the existing files

});

async.parallel([

function () { },

function () { }

], callback);

async.series([

function () { },

function () { }

]);

Page 37: Node.js 101

Request is designed to be the simplest way possible to make http calls. It supports HTTPS, streaming and follows redirects by default.

var request = require('request');

request('http://www.microsoft.com', function (error, response, body) {

if (!error && response.statusCode == 200) {

console.log(body);

}

});

Page 38: Node.js 101

• Socket.IO enables real-time bidirectional event-based communication using WebSockets.

• Requires HTTP module.

• Can broadcast to other sockets.

Page 39: Node.js 101

• Express is a minimal, open source and flexible node.js web app framework designed to make developing websites, web apps and APIs much easier.

• Express helps you respond to requests with route support so that you may write responses to specific URLs. Express allows you to support multiple templating engines to simplify generating HTML.

Page 40: Node.js 101

var express = require('express'); var app = express();

app.get('/', function (req, res) { res.json({message:'hooray! welcome to our api!'});

});

app.listen(process.env.PORT || 8080);

Page 41: Node.js 101
Page 42: Node.js 101
Page 43: Node.js 101

• Node.js Basics and Environment

• Node Package Manager Overview

• Web Framework Express Basics

• WebSockets and Socket.io basics

• Building a Chatroom using Node.js

Page 44: Node.js 101

Follow @ramisayar

A chatroom for all! articles: aka.ms/node-101

Page 45: Node.js 101

©2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, Office, Azure, System Center, Dynamics and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.