# 1.

INTRODUCTION

Q. What is [Link]?
[Link] is an open-source server side runtime environment built on
Chrome's V8 JavaScript engine. It provides an event driven, non-blocking
(asynchronous) I/O and cross-platform runtime environment for building
highly scalable server-side applications using JavaScript.

Q. What is [Link] Process Model?

[Link] runs in a single process and the application code runs in a single
thread and thereby needs less resources than other platforms.

All the user requests to your web application will be handled by a single
thread and all the I/O work or long running job is performed
asynchronously for a particular request. So, this single thread doesn't
have to wait for the request to complete and is free to handle the next
request. When asynchronous I/O work completes then it processes the
request further and sends the response.

Q. What are the key features of [Link]?

 Asynchronous and Event driven – All APIs of [Link] are
asynchronous. This feature means that if a Node receives a request
for some Input/Output operation, it will execute that operation in the
background and continue with the processing of other requests.
Thus it will not wait for the response from the previous requests.
 Fast in Code execution – [Link] uses the V8 JavaScript Runtime
engine, the one which is used by Google Chrome. Node has a
wrapper over the JavaScript engine which makes the runtime engine
much faster and hence processing of requests within [Link] also
become faster.
 Single Threaded but Highly Scalable – [Link] uses a single
thread model for event looping. The response from these events
may or may not reach the server immediately. However, this does
not block other operations. Thus making [Link] highly scalable.
Traditional servers create limited threads to handle requests while
[Link] creates a single thread that provides service to much larger
numbers of such requests.
  [Link] library uses JavaScript – This is another important
aspect of [Link] from the developer's point of view. The majority of
developers are already well-versed in JavaScript. Hence,
development in [Link] becomes easier for a developer who knows
JavaScript.
 There is an Active and vibrant community for the [Link]
framework – The active community always keeps the framework
updated with the latest trends in the web development.
 No Buffering – [Link] applications never buffer any data. They
simply output the data in chunks.

Q. Explain how does [Link] work?

A [Link] application creates a single thread on its invocation. Whenever
[Link] receives a request, it first completes its processing before moving
on to the next request.

[Link] works asynchronously by using the event loop and callback

functions, to handle multiple requests coming in parallel. An Event Loop is
a functionality which handles and processes all your external events and
just converts them to a callback function. It invokes all the event handlers
at a proper time. Thus, lots of work is done on the back-end, while
processing a single request, so that the new incoming request doesn't
have to wait if the processing is not complete.

While processing a request, [Link] attaches a callback function to it and

moves it to the back-end. Now, whenever its response is ready, an event
is called which triggers the associated callback function to send this
response.

# 2. [Link] SETUP

Q. How to create a simple server in [Link]

that returns Hello World?
Step 01: Create a project directory

mkdir myapp
cd myapp
Step 02: Initialize project and link it to npm

npm init
This creates a [Link] file in your myapp folder. The file contains
references for all npm packages you have downloaded to your project.
The command will prompt you to enter a number of things. You can enter
your way through all of them EXCEPT this one:

entry point: ([Link])

Rename this to:

[Link]
Step 03: Install Express in the myapp directory

npm install express --save

Step 04: [Link]

/**
* [Link]
*/
const express = require('express');
const app = express();

[Link]('/', function (req, res) {

[Link]('Hello World!');
});

[Link](3000, function () {
[Link]('App listening on port 3000!');
});

Q. Explain the concept of URL module in

[Link]?
The URL module in [Link] splits up a web address into readable parts.
Use require() to include the module. Then parse an address with
the [Link]() method, and it will return a URL object with each part of
the address as properties.

Example:

/**
* URL Module in [Link]
*/
const url = require('url');
const adr = '[Link]
const q = [Link](adr, true);

[Link]([Link]); // localhost:8080
[Link]([Link]); // "/[Link]"
[Link]([Link]); // "?year=2022&month=september"

const qdata = [Link]; // { year: 2022, month: 'september' }

[Link]([Link]); // "september"
# 3. [Link] DATA TYPES

Q. What are the data types in [Link]?

Just like JS, there are two categories of data types in Node: Primitives and
Objects.

1. Primitives:

 String
 Number
 BigInt
 Boolean
 Undefined
 Null
 Symbol

2. Objects:

 Function
 Array
 Buffer

Q. Explain String data type in [Link]?

Strings in [Link] are sequences of unicode characters. Strings can be
wrapped in a single or double quotation marks. Javascript provide many
functions to operate on string, like indexOf(), split(), substr(), length.

String functions:

Function Description
charAt() It is useful to find a specific character present in a string.
Concat() It is useful to concat more than one string.
indexOf(
It is useful to get the index of a specified character or a part of the string.
)
Match() It is useful to match multiple strings.
Split() It is useful to split the string and return an array of string.
 Function Description
It is useful to join the array of strings and those are separated by comma (,)
Join()
operator.
Example:

/**
* String Data Type
*/
const str1 = "Hello";
const str2 = 'World';

[Link]("Concat Using (+) :" , (str1 + ' ' + str2));

[Link]("Concat Using Function :" , ([Link](str2)));

Q. Explain Number data type in [Link]?

The number data type in [Link] is 64 bits floating point number both
positive and negative. The parseInt() and parseFloat() functions are used
to convert to number, if it fails to convert into a number then it
returns NaN.

Example:

/**
* Number Data Type
*/
// Example 01:
const num1 = 10;
const num2 = 20;

[Link](`sum: ${num1 + num2}`);

// Example 02:
[Link](parseInt("32")); // 32
[Link](parseFloat("8.24")); // 8.24
[Link](parseInt("234.12345")); // 234
[Link](parseFloat("10")); // 10

// Example 03:
[Link](isFinite(10/5)); // true
[Link](isFinite(10/0)); // false

// Example 04:
[Link](5 / 0); // Infinity
[Link](-5 / 0); // -Infinity

Q. Explain BigInt data type in [Link]?

A BigInt value, also sometimes just called a BigInt, is a bigint primitive,
created by appending n to the end of an integer literal, or by calling the
BigInt() function ( without the new operator ) and giving it an integer
value or string value.

Example:

/**
* BigInt Data Type
*/
const maxSafeInteger = 99n; // This is a BigInt
const num2 = BigInt('99'); // This is equivalent
const num3 = BigInt(99); // Also works

typeof 1n === 'bigint' // true

typeof BigInt('1') === 'bigint' // true

Q. Explain Boolean data type in [Link]?

Boolean data type is a data type that has one of two possible values,
either true or false. In programming, it is used in logical representation or
to control program structure.

The boolean() function is used to convert any data type to a boolean

value. According to the rules, false, 0, NaN, null, undefined, empty string
evaluate to false and other values evaluates to true.

Example:

/**
* Boolean Data Type
*/
// Example 01:
const isValid = true;
[Link](isValid); // true

// Example 02:
[Link](true && true); // true
[Link](true && false); // false
[Link](true || false); // true
[Link](false || false); // false
[Link](!true); // false
[Link](!false); // true

Q. Explain Undefined and Null data type in

[Link]?
In [Link], if a variable is defined without assigning any value, then that
will take undefined as value. If we assign a null value to the variable,
then the value of the variable becomes null.

Example:
/**
* NULL and UNDEFINED Data Type
*/
let x;
[Link](x); // undefined

let y = null;
[Link](y); // null

Q. Explain Symbol data type in [Link]?

Symbol is an immutable primitive value that is unique. It's a very peculiar
data type. Once you create a symbol, its value is kept private and for
internal use.

Example:

/**
* Symbol Data Type
*/
const NAME = Symbol()
const person = {
[NAME]: 'Ritika Bhavsar'
}

person[NAME] // 'Ritika Bhavsar'

Q. Explain function in [Link]?

Functions are first class citizens in Node's JavaScript, similar to the
browser's JavaScript. A function can have attributes and properties also. It
can be treated like a class in JavaScript.

Example:

/**
* Function in [Link]
*/
function Messsage(name) {
[Link]("Hello "+name);
}

Messsage("World"); // Hello World

Q. Explain Buffer data type in [Link]?

[Link] includes an additional data type called Buffer ( not available in
browser's JavaScript ). Buffer is mainly used to store binary data, while
reading from a file or receiving packets over the network.
Example:

/**
* Buffer Data Type
*/
let b = new Buffer(10000);
let str = "----------";

[Link](str);
[Link]( [Link] ); // 10
[Link]( [Link] ); // 10000
Note: Buffer() is deprecated due to security and usability issues.

# 4. [Link] ARCHITECTURE

Q. How does [Link] works?

[Link] is completely event-driven. Basically the server consists of one
thread processing one event after another.

A new request coming in is one kind of event. The server starts processing
it and when there is a blocking IO operation, it does not wait until it
completes and instead registers a callback function. The server then
immediately starts to process another event ( maybe another request ).
When the IO operation is finished, that is another kind of event, and the
server will process it ( i.e. continue working on the request ) by executing
the callback as soon as it has time.

[Link] Platform does not follow Request/Response Multi-Threaded

Stateless Model. It follows Single Threaded with Event Loop Model. [Link]
Processing model mainly based on Javascript Event based model with
Javascript callback mechanism.

Single Threaded Event Loop Model Processing Steps:

  Clients Send request to Web Server.
 [Link] Web Server internally maintains a Limited Thread pool to
provide services to the Client Requests.
 [Link] Web Server receives those requests and places them into a
Queue. It is known as Event Queue.
 [Link] Web Server internally has a Component, known as Event
Loop. Why it got this name is that it uses indefinite loop to receive
requests and process them.
 Event Loop uses Single Thread only. It is main heart of [Link]
Platform Processing Model.
 Event Loop checks any Client Request is placed in Event Queue. If
no, then wait for incoming requests for indefinitely.
 If yes, then pick up one Client Request from Event Queue
o Starts process that Client Request
o If that Client Request Does Not requires any Blocking IO
Operations, then process everything, prepare response and
send it back to client.
o If that Client Request requires some Blocking IO Operations
like interacting with Database, File System, External Services
then it will follow different approach
 Checks Threads availability from Internal Thread Pool
 Picks up one Thread and assign this Client Request to
that thread.
 That Thread is responsible for taking that request,
process it, perform Blocking IO operations, prepare
response and send it back to the Event Loop
 Event Loop in turn, sends that Response to the
respective Client.

Q. What are the core modules of [Link]?

[Link] has a set of core modules that are part of the platform and come
with the [Link] installation. These modules can be loaded into the
program by using the require function.

Syntax:

const module = require('module_name');

Example:

const http = require('http');

[Link](function (req, res) {

[Link](200, {'Content-Type': 'text/html'});
[Link]('Welcome to [Link]!');
[Link]();
}).listen(3000);
The following table lists some of the important core modules in [Link].

Core
Description
Module
assert provides a set of assertion functions useful for testing
console provides a simple debugging console
crypto provides cryptographic functionality
http module includes classes, methods and events to create [Link] http
http
server.
url url module includes methods for URL resolution and parsing.
querystring querystring module includes methods to deal with query string.
path path module includes methods to deal with file paths.
fs fs module includes classes, methods, and events to work with file I/O.
util util module includes utility functions useful for programmers.

Q. What do you understand by Reactor

Pattern in [Link]?
Reactor Pattern is used to avoid the blocking of the Input/Output
operations. It provides us with a handler that is associated with I/O
operations. When the I/O requests are to be generated, they get
submitted to a demultiplexer, which handles concurrency in avoiding the
blocking of the I/O mode and collects the requests in form of an event and
queues those events.

There are two ways in which I/O operations are performed:

1. Blocking I/O: Application will make a function call and pause its
execution at a point until the data is received. It is called as
"Synchronous".

2. Non-Blocking I/O: Application will make a function call, and, without

waiting for the results it continues its execution. It is called as
"Asynchronous".
Reactor Pattern comprises of:

1. Resources: They are shared by multiple applications for I/O

operations, generally slower in executions.

2. Synchronous Event De-multiplexer/Event Notifier: This uses

Event Loop for blocking on all resources. When a set of I/O operations
completes, the Event De-multiplexer pushes the new events into the
Event Queue.

3. Event Loop and Event Queue: Event Queue queues up the new
events that occurred along with its event-handler, pair.

4. Request Handler/Application: This is, generally, the application that

provides the handler to be executed for registered events on resources.

Q. What are the global objects of [Link]?

[Link] Global Objects are the objects that are available in all modules.
Global Objects are built-in objects that are part of the JavaScript and can
be used directly in the application without importing any particular
module.
These objects are modules, functions, strings and object itself as
explained below.

1. global:

It is a global namespace. Defining a variable within this namespace makes

it globally accessible.

var myvar;
2. process:

It is an inbuilt global object that is an instance of EventEmitter used to get

information on current process. It can also be accessed using require()
explicitly.

3. console:

It is an inbuilt global object used to print to stdout and stderr.

[Link]("Hello World"); // Hello World

4. setTimeout(), clearTimeout(), setInterval(), clearInterval():

The built-in timer functions are globals

function printHello() {
[Link]( "Hello, World!");
}

// Now call above function after 2 seconds

var timeoutObj = setTimeout(printHello, 2000);
5. __dirname:

It is a string. It specifies the name of the directory that currently contains

the code.

[Link](__dirname);
6. __filename:

It specifies the filename of the code being executed. This is the resolved
absolute path of this code file. The value inside a module is the path to
that module file.

[Link](__filename);

Q. What is chrome v8 engine?

V8 is a C++ based open-source JavaScript engine developed by Google. It
was originally designed for Google Chrome and Chromium-based browsers
( such as Brave ) in 2008, but it was later utilized to create [Link] for
server-side coding.
V8 is the JavaScript engine i.e. it parses and executes JavaScript code. The
DOM, and the other Web Platform APIs ( they all makeup runtime
environment ) are provided by the browser.

V8 is known to be a JavaScript engine because it takes JavaScript code

and executes it while browsing in Chrome. It provides a runtime
environment for the execution of JavaScript code. The best part is that the
JavaScript engine is completely independent of the browser in which it
runs.

Q. Why is LIBUV needed in Node JS?

libuv is a C library originally written for [Link] to abstract non-blocking
I/O operations. It provide the below features

 It allows the CPU and other resources to be used simultaneously

while still performing I/O operations, thereby resulting in efficient
use of resources and network.
 It facilitates an event-driven approach wherein I/O and other
activities are performed using callback-based notifications.
 It provides mechanisms to handle file system, DNS, network, child
processes, pipes, signal handling, polling and streaming
 It also includes a thread pool for offloading work for some things
that can't be done asynchronously at the operating system level.

Q. How V8 compiles JavaScript code?

Compilation is the process of converting human-readable code to machine
code. There are two ways to compile the code

 Using an Interpreter: The interpreter scans the code line by line

and converts it into byte code.
 Using a Compiler: The Compiler scans the entire document and
compiles it into highly optimized byte code.

The V8 engine uses both a compiler and an interpreter and follows just-
in-time (JIT) compilation to speed up the execution. JIT compiling works
by compiling small portions of code that are just about to be executed.
This prevents long compilation time and the code being compiles is only
that which is highly likely to run.

# 5. [Link] EVENTS
Q. What is EventEmitter in [Link]?
The EventEmitter is a class that facilitates communication/interaction
between objects in [Link]. The EventEmitter class can be used to create
and handle custom events.

EventEmitter is at the core of Node asynchronous event-driven

architecture. Many of Node's built-in modules inherit from EventEmitter
including prominent frameworks like [Link]. An emitter object
basically has two main features:

 Emitting name events.

 Registering and unregistering listener functions.

Example 01: Create an event emitter instance and register a couple of

callbacks

/**
* Callbacks Events
*/
const events = require('events');
const eventEmitter = new [Link]();

function listenerOne() {
[Link]('First Listener Executed');
}

function listenerTwo() {
[Link]('Second Listener Executed');
}

[Link]('listenerOne', listenerOne); // Register for listenerOne

[Link]('listenerOne', listenerTwo); // Register for listenerOne

// When the event "listenerOne" is emitted, both the above callbacks should
be invoked.
[Link]('listenerOne');

// Output
First Listener Executed
Second Listener Executed
Example 02: Registering for the event to be fired only one time
using once.

/**
* Emit Events Once
*/
const events = require('events');
const eventEmitter = new [Link]();

function listenerOnce() {
[Link]('listenerOnce fired once');
}
[Link]('listenerOne', listenerOnce); // Register listenerOnce
[Link]('listenerOne');

// Output
listenerOnce fired once
Example 03: Registering for the event with callback parameters

/**
* Callback Events with Parameters
*/
const events = require('events');
const eventEmitter = new [Link]();

function listener(code, msg) {

[Link](`status ${code} and ${msg}`);
}

[Link]('status', listener); // Register listener

[Link]('status', 200, 'ok');

// Output
status 200 and ok

Q. How the Event Loop Works in [Link]?

The event loop allows [Link] to perform non-blocking I/O operations
despite the fact that JavaScript is single-threaded. It is done by offloading
operations to the system kernel whenever possible.

[Link] is a single-threaded application, but it can

support concurrency via the concept of event and callbacks. Every API
of [Link] is asynchronous and being single-threaded, they use async
function calls to maintain concurrency. Node uses observer pattern.
Node thread keeps an event loop and whenever a task gets completed, it
fires the corresponding event which signals the event-listener function to
execute.

Features of Event Loop:

 Event loop is an endless loop, which waits for tasks, executes them
and then sleeps until it receives more tasks.
 The event loop executes tasks from the event queue only when the
call stack is empty i.e. there is no ongoing task.
 The event loop allows us to use callbacks and promises.
 The event loop executes the tasks starting from the oldest first.
Example:

/**
* Event loop in [Link]
*/
const events = require('events');
const eventEmitter = new [Link]();

// Create an event handler as follows

const connectHandler = function connected() {
[Link]('connection succesful.');
[Link]('data_received');
}

// Bind the connection event with the handler

[Link]('connection', connectHandler);

// Bind the data_received event with the anonymous function

[Link]('data_received', function() {
[Link]('data received succesfully.');
});

// Fire the connection event

[Link]('connection');
[Link]("Program Ended.");

// Output
Connection succesful.
Data received succesfully.
Program Ended.

Q. What is the difference between

[Link]() and setImmediate()?
1. [Link]():

The [Link]() method adds the callback function to the start of

the next event queue. It is to be noted that, at the start of the program
[Link]() method is called for the first time before the event loop
is processed.

2. setImmdeiate():

The setImmediate() method is used to execute a function right after the

current event loop finishes. It is callback function is placed in the check
phase of the next event queue.

Example:

/**
* setImmediate() and [Link]()
*/
setImmediate(() => {
[Link]("1st Immediate");
});

setImmediate(() => {
[Link]("2nd Immediate");
});

[Link](() => {
[Link]("1st Process");
});

[Link](() => {
[Link]("2nd Process");
});

// First event queue ends here

[Link]("Program Started");

// Output
Program Started
1st Process
2nd Process
1st Immediate
2nd Immediate

Q. What is callback function in [Link]?

A callback is a function which is called when a task is completed, thus
helps in preventing any kind of blocking and a callback function allows
other code to run in the meantime.

Callback is called when task get completed and is asynchronous

equivalent for a function. Using Callback concept, [Link] can process a
large number of requests without waiting for any function to return the
result which makes [Link] highly scalable.

Example:

/**
* Callback Function
*/
function myAsync(a, b, callback) {
setTimeout(function () {
callback(a + b);
}, 100);
}
[Link]("Before Asynchronous Call");

myAsync(10, 20, function (result) {

[Link]("Sum: " + result);
});
[Link]("After Asynchronous Call");

// Output
Before Asynchronous Call
After Asynchronous Call
Sum: 30

Q. What are the difference between Events

and Callbacks?
1. Events:

[Link] events module which emits named events that can cause
corresponding functions or callbacks to be called. Functions ( callbacks )
listen or subscribe to a particular event to occur and when that event
triggers, all the callbacks subscribed to that event are fired one by one in
order to which they were registered.

All objects that emit events are instances of the EventEmitter class. The
event can be emitted or listen to an event with the help of EventEmitter

Example:

/**
* Events Module
*/
const event = require('events');
const eventEmitter = new [Link]();

// add listener function for Sum event

[Link]('Sum', function(num1, num2) {
[Link]('Total: ' + (num1 + num2));
});

// call event
[Link]('Sum', 10, 20);

// Output
Total: 30
2. Callbacks:

A callback function is a function passed into another function as an

argument, which is then invoked inside the outer function to complete
some kind of routine or action.

Example:

/**
* Callbacks
*/
function sum(number) {
[Link]('Total: ' + number);
}

function calculator(num1, num2, callback) {

let total = num1 + num2;
callback(total);
}

calculator(10, 20, sum);

// Output
Total: 30
Callback functions are called when an asynchronous function returns its
result, whereas event handling works on the observer pattern. The
functions that listen to events act as Observers. Whenever an event gets
fired, its listener function starts executing. [Link] has multiple in-built
events available through events module and EventEmitter class which are
used to bind events and event-listeners

Q. What is an error-first callback?

The pattern used across all the asynchronous methods in [Link] is
called Error-first Callback. Here is an example:

[Link]( "[Link]", function ( err, data ) {

if ( err ) {
[Link]( err );
}
[Link]( data );
});
Any asynchronous method expects one of the arguments to be a callback.
The full callback argument list depends on the caller method, but the first
argument is always an error object or null. When we go for the
asynchronous method, an exception thrown during function execution
cannot be detected in a try/catch statement. The event happens after the
JavaScript engine leaves the try block.
In the preceding example, if any exception is thrown during the reading of
the file, it lands on the callback function as the first and mandatory
parameter.

Q. What is callback hell in [Link]?

The callback hell contains complex nested callbacks. Here, every callback
takes an argument that is a result of the previous callbacks. In this way,
the code structure looks like a pyramid, making it difficult to read and
maintain. Also, if there is an error in one function, then all other functions
get affected.

An asynchronous function is one where some external activity must

complete before a result can be processed; it is "asynchronous" in the
sense that there is an unpredictable amount of time before a result
becomes available. Such functions require a callback function to handle
errors and process the result.

Example:

/**
* Callback Hell
*/
getData(function(a){
getMoreData(a, function(b){
getMoreData(b, function(c){
getMoreData(c, function(d){
getMoreData(d, function(e){
...
});
});
});
});
});

Q. How to avoid callback hell in [Link]?

1. Managing callbacks using [Link]:

Async is a really powerful npm module for managing asynchronous nature

of JavaScript. Along with [Link], it also works for JavaScript written for
browsers.

Async provides lots of powerful utilities to work with asynchronous

processes under different scenarios.

npm install --save async

2. Managing callbacks hell using promises:
Promises are alternative to callbacks while dealing with asynchronous
code. Promises return the value of the result or an error exception. The
core of the promises is the .then() function, which waits for the promise
object to be returned.

The .then() function takes two optional functions as arguments and

depending on the state of the promise only one will ever be called. The
first function is called when the promise if fulfilled (A successful result).
The second function is called when the promise is rejected.

Example:

/**
* Promises
*/
const myPromise = new Promise((resolve, reject) => {
setTimeout(() => {
resolve("Successful!");
}, 300);
});
3. Using Async Await:

Async await makes asynchronous code look like it's synchronous. This has
only been possible because of the reintroduction of promises into [Link].
Async-Await only works with functions that return a promise.

Example:

/**
* Async Await
*/
const getrandomnumber = function(){
return new Promise((resolve, reject)=>{
setTimeout(() => {
resolve([Link]([Link]() * 20));
}, 1000);
});
}

const addRandomNumber = async function(){

const sum = await getrandomnumber() + await getrandomnumber();
[Link](sum);
}

addRandomNumber();

Q. What is typically the first argument

passed to a callback handler?
The first parameter of the callback is the error value. If the function hits
an error, then they typically call the callback with the first parameter
being an Error object.
Example:

/**
* Callback Handler
*/
const Division = (numerator, denominator, callback) => {
if (denominator === 0) {
callback(new Error('Divide by zero error!'));
} else {
callback(null, numerator / denominator);
}
};

// Function Call
Division(5, 0, (err, result) => {
if (err) {
return [Link]([Link]);
}
[Link](`Result: ${result}`);
});

Q. What are the timing features of [Link]?

The Timers module in [Link] contains functions that execute code after a
set period of time. Timers do not need to be imported via require(), since
all the methods are available globally to emulate the browser JavaScript
API.

Some of the functions provided in this module are

1. setTimeout():

This function schedules code execution after the assigned amount of time
( in milliseconds ). Only after the timeout has occurred, the code will be
executed. This method returns an ID that can be used
in clearTimeout() method.

Syntax:

setTimeout(callback, delay, args )

Example:

function printMessage(arg) {
[Link](`${arg}`);
}

setTimeout(printMessage, 1000, 'Display this Message after 1 seconds!');

2. setImmediate():

The setImmediate() method executes the code at the end of the current
event loop cycle. The function passed in the setImmediate() argument is a
function that will be executed in the next iteration of the event loop.
Syntax:

setImmediate(callback, args)
Example:

// Setting timeout for the function

setTimeout(function () {
[Link]('setTimeout() function running...');
}, 500);

// Running this function immediately before any other

setImmediate(function () {
[Link]('setImmediate() function running...');
});

// Directly printing the statement

[Link]('Normal statement in the event loop');

// Output
// Normal statement in the event loop
// setImmediate() function running...
// setTimeout() function running...
3. setInterval():

The setInterval() method executes the code after the specified interval.
The function is executed multiple times after the interval has passed. The
function will keep on calling until the process is stopped externally or
using code after specified time period. The clearInterval() method can be
used to prevent the function from running.

Syntax:

setInterval(callback, delay, args)

Example:

setInterval(function() {
[Link]('Display this Message intervals of 1 seconds!');
}, 1000);

# 6. [Link] FILE SYSTEM

Q. How [Link] read the content of a file?

The "normal" way in [Link] is probably to read in the content of a file in a
non-blocking, asynchronous way. That is, to tell Node to read in the file,
and then to get a callback when the file-reading has been finished. That
would allow us to hand several requests in parallel.

Common use for the File System module:

  Read files
 Create files
 Update files
 Delete files
 Rename files

Read Files
[Link]

<html>
<body>
<h1>My Header</h1>
<p>My paragraph.</p>
</body>
</html>
/**
* read_file.js
*/
const http = require('http');
const fs = require('fs');
[Link](function (req, res) {
[Link]('[Link]', function(err, data) {
[Link](200, {'Content-Type': 'text/html'});
[Link](data);
[Link]();
});
}).listen(8080);
Initiate read_file.js:

node read_file.js

# 7. [Link] STREAMS

Q. How many types of streams are present

in [Link]?
Streams are objects that let you read data from a source or write data to a
destination in continuous fashion. There are four types of streams

 Readable − Stream which is used for read operation.

 Writable − Stream which is used for write operation.
 Duplex − Stream which can be used for both read and write
operation.
 Transform − A type of duplex stream where the output is
computed based on input.
Each type of Stream is an EventEmitter instance and throws several
events at different instance of times.

Example:

 data − This event is fired when there is data is available to read.

 end − This event is fired when there is no more data to read.
 error − This event is fired when there is any error receiving or
writing data.
 finish − This event is fired when all the data has been flushed to
underlying system.

Reading from a Stream:

const fs = require("fs");
const data = '';

// Create a readable stream

const readerStream = [Link]('[Link]');

// Set the encoding to be utf8.

[Link]('UTF8');

// Handle stream events --> data, end, and error

[Link]('data', function(chunk) {
data += chunk;
});

[Link]('end',function() {
[Link](data);
});

[Link]('error', function(err) {
[Link]([Link]);
});

[Link]("Program Ended");
Writing to a Stream:

const fs = require("fs");
const data = 'Simply Easy Learning';

// Create a writable stream

const writerStream = [Link]('[Link]');

// Write the data to stream with encoding to be utf8

[Link](data,'UTF8');

// Mark the end of file

[Link]();

// Handle stream events --> finish, and error

[Link]('finish', function() {
[Link]("Write completed.");
});

[Link]('error', function(err) {
 [Link]([Link]);
});

[Link]("Program Ended");
Piping the Streams:

Piping is a mechanism where we provide the output of one stream as the

input to another stream. It is normally used to get data from one stream
and to pass the output of that stream to another stream. There is no limit
on piping operations.

const fs = require("fs");

// Create a readable stream

const readerStream = [Link]('[Link]');

// Create a writable stream

const writerStream = [Link]('[Link]');

// Pipe the read and write operations

// read [Link] and write data to [Link]
[Link](writerStream);

[Link]("Program Ended");
Chaining the Streams:

Chaining is a mechanism to connect the output of one stream to another

stream and create a chain of multiple stream operations. It is normally
used with piping operations.

const fs = require("fs");
const zlib = require('zlib');

// Compress the file [Link] to [Link]

[Link]('[Link]')
.pipe([Link]())
.pipe([Link]('[Link]'));

[Link]("File Compressed.");

# 8. [Link] MULTITHREADING

Q. Is [Link] entirely based on a single-

thread?
Yes, it is true that [Link] processes all requests on a single thread. But it
is just a part of the theory behind [Link] design. In fact, more than the
single thread mechanism, it makes use of events and callbacks to handle
a large no. of requests asynchronously.
Moreover, [Link] has an optimized design which utilizes both JavaScript
and C++ to guarantee maximum performance. JavaScript executes at the
server-side by Google Chrome v8 engine. And the C++ lib UV library takes
care of the non-sequential I/O via background workers.

To explain it practically, let's assume there are 100s of requests lined up

in [Link] queue. As per design, the main thread of [Link] event loop will
receive all of them and forwards to background workers for execution.
Once the workers finish processing requests, the registered callbacks get
notified on event loop thread to pass the result back to the user.

Q. How does [Link] handle child threads?

[Link] is a single threaded language which in background uses multiple
threads to execute asynchronous code. [Link] is non-blocking which
means that all functions ( callbacks ) are delegated to the event loop and
they are ( or can be ) executed by different threads. That is handled by
[Link] run-time.

 Nodejs Primary application runs in an event loop, which is in a single

thread.
 Background I/O is running in a thread pool that is only accessible to
C/C++ or other compiled/native modules and mostly transparent to
the JS.
 Node v11/12 now has experimental worker_threads, which is
another option.
 [Link] does support forking multiple processes ( which are
executed on different cores ).
 It is important to know that state is not shared between master and
forked process.
 We can pass messages to forked process ( which is different script )
and to master process from forked process with function send.

Q. How does [Link] support multi-

processor platforms, and does it fully utilize
all processor resources?
Since [Link] is by default a single thread application, it will run on a
single processor core and will not take full advantage of multiple core
resources. However, [Link] provides support for deployment on multiple-
core systems, to take greater advantage of the hardware. The Cluster
module is one of the core [Link] modules and it allows running multiple
[Link] worker processes that will share the same port.
The cluster module helps to spawn new processes on the operating
system. Each process works independently, so you cannot use shared
state between child processes. Each process communicates with the main
process by IPC and pass server handles back and forth.

Cluster supports two types of load distribution:

 The main process listens on a port, accepts new connection and

assigns it to a child process in a round robin fashion.
 The main process assigns the port to a child process and child
process itself listen the port.

Q. Since node is a single threaded process,

how to make use of all CPUs?
[Link] is a single threaded language which in background uses multiple
threads to execute asynchronous code. [Link] is non-blocking which
means that all functions ( callbacks ) are delegated to the event loop and
they are ( or can be ) executed by different threads. That is handled by
[Link] run-time.

 [Link] does support forking multiple processes ( which are

executed on different cores ).
 It is important to know that state is not shared between master and
forked process.
 We can pass messages to forked process ( which is different script )
and to master process from forked process with function send.

A single instance of [Link] runs in a single thread. To take advantage of

multi-core systems, the user will sometimes want to launch a cluster of
[Link] processes to handle the load. The cluster module allows easy
creation of child processes that all share server ports.

const cluster = require('cluster');

const http = require('http');
const numCPUs = require('os').cpus().length;

if ([Link]) {
[Link](`Master ${[Link]} is running`);

// Fork workers.
for (let i = 0; i < numCPUs; i++) {
[Link]();
}

[Link]('exit', (worker, code, signal) => {

[Link](`worker ${[Link]} died`);
});
} else {
 // Workers can share any TCP connection
// In this case it is an HTTP server
[Link]((req, res) => {
[Link](200);
[Link]('hello world\n');
}).listen(8000);

[Link](`Worker ${[Link]} started`);

}
Running [Link] will now share port 8000 between the workers:

$ node [Link]
Master 3596 is running
Worker 4324 started
Worker 4520 started
Worker 6056 started
Worker 5644 started
The worker processes are spawned using the child_process.fork() method,
so that they can communicate with the parent via IPC and pass server
handles back and forth.

The cluster module supports two methods of distributing incoming

connections.

The first one (and the default one on all platforms except Windows), is the
round-robin approach, where the master process listens on a port, accepts
new connections and distributes them across the workers in a round-robin
fashion, with some built-in smarts to avoid overloading a worker process.

The second approach is where the master process creates the listen
socket and sends it to interested workers. The workers then accept
incoming connections directly.

Q. If [Link] is single threaded then how it

handles concurrency?
Node js despite being single-threaded is the asynchronous nature that
makes it possible to handle concurrency and perform multiple I/O
operations at the same time. Node js uses an event loop to maintain
concurrency and perform non-blocking I/O operations.

As soon as Node js starts, it initializes an event loop. The event loop works
on a queue (which is called an event queue) and performs tasks in FIFO
(First In First Out) order. It executes a task only when there is no ongoing
task in the call stack. The call stack works in LIFO(Last In First Out) order.
The event loop continuously checks the call stack to check if there is any
task that needs to be run. Now whenever the event loop finds any
function, it adds it to the stack and runs in order.
Example:

/**
* Concurrency
*/
function add(a, b) {
return a + b;
}

function print(n) {
[Link](`Two times the number ${n} is ` + add(n, n));
}

print(5);
Here, the function print(5) will be invoked and will push into the call
stack. When the function is called, it starts consoling the statement inside
it but before consoling the whole statement it encounters another function
add(n,n) and suspends its current execution, and pushes the add function
into the top of the call stack.

Now the function will return the addition a+b and then popped out from
the stack and now the previously suspended function will start running
and will log the output to console and then this function too will get pop
from the stack and now the stack is empty. So this is how a call stack
works.

Q. How to kill child processes that spawn

their own child processes in [Link]?
If a child process in [Link] spawn their own child processes, kill() method
will not kill the child process's own child processes. For example, if I start
a process that starts it's own child processes via child_process module,
killing that child process will not make my program to quit.

const spawn = require('child_process').spawn;

const child = spawn('my-command');

[Link]();
The program above will not quit if my-command spins up some more
processes.

PID range hack:

We can start child processes with {detached: true} option so those

processes will not be attached to main process but they will go to a new
group of processes. Then using [Link](-pid) method on main process
we can kill all processes that are in the same group of a child process with
the same pid group. In my case, I only have one processes in this group.

const spawn = require('child_process').spawn;

const child = spawn('my-command', {detached: true});

[Link](-[Link]);
Please note - before pid. This converts a pid to a group of pids for process
kill() method.

Q. How to synchronize data between

multiple clients on [Link] server?
ToDo

# 9. [Link] WEB MODULE

Q. How to use JSON Web Token (JWT) for

authentication in [Link]?
JSON Web Token (JWT) is an open standard that defines a compact and
self-contained way of securely transmitting information between parties
as a JSON object. This information can be verified and trusted because it is
digitally signed.

There are some advantages of using JWT for authorization:

 Purely stateless. No additional server or infra required to store

session information.
 It can be easily shared among services.

Syntax:

[Link](payload, secretOrPrivateKey, [options, callback])

 Header - Consists of two parts: the type of token (i.e., JWT) and the
signing algorithm (i.e., HS512)
 Payload - Contains the claims that provide information about a user
who has been authenticated along with other information such as
token expiration time.
 Signature - Final part of a token that wraps in the encoded header
and payload, along with the algorithm and a secret

Installation:

npm install jsonwebtoken bcryptjs --save

Example:

/**
* [Link]
*/
const express = require('express');
const router = [Link]();
const bodyParser = require('body-parser');
const User = require('../user/User');

const jwt = require('jsonwebtoken');

const bcrypt = require('bcryptjs');
const config = require('../config');

[Link]([Link]({ extended: false }));

[Link]([Link]());

[Link]('/register', function(req, res) {

let hashedPassword = [Link]([Link], 8);

[Link]({
name : [Link],
email : [Link],
password : hashedPassword
},
function (err, user) {
if (err) return [Link](500).send("There was a problem registering
the user.")
// create a token
let token = [Link]({ id: user._id }, [Link], {
expiresIn: 86400 // expires in 24 hours
});
[Link](200).send({ auth: true, token: token });
});
});
[Link]:

/**
* [Link]
*/
[Link] = {
'secret': 'supersecret'
};
The [Link]() method takes a payload and the secret key defined
in [Link] as parameters. It creates aunique string of characters
representing the payload. In our case, the payload is an object containing
only the id of the user.

Reference:

 [Link]
Q. How to build a microservices
architecture with [Link]?
Microservices are a style of Service Oriented Architecture
(SOA) where the app is structured on an assembly of interconnected
services. With microservices, the application architecture is built with
lightweight protocols. The services are finely seeded in the architecture.
Microservices disintegrate the app into smaller services and enable
improved modularity.

There are few things worth emphasizing about the superiority of

microservices, and distributed systems generally, over monolithic
architecture:

 Modularity — responsibility for specific operations is assigned to

separate pieces of the application
 Uniformity — microservices interfaces (API endpoints) consist of a
base URI identifying a data object and standard HTTP methods (GET,
POST, PUT, PATCH and DELETE) used to manipulate the object
 Robustness — component failures cause only the absence or
reduction of a specific unit of functionality
  Maintainability — system components can be modified and
deployed independently
 Scalability — instances of a service can be added or removed to
respond to changes in demand.
 Availability — new features can be added to the system while
maintaining 100% availability.
 Testability — new solutions can be tested directly in the
production environment by implementing them for restricted
segments of users to see how they behave in real life.

Example: Creating Microservices with [Link]

Step 01: Creating a Server to Accept Requests

This file is creating our server and assigns routes to process all requests.

// [Link]

const express = require('express')

const app = express();
const port = [Link] || 3000;

const routes = require('./api/routes');

routes(app);
[Link](port, function() {
[Link]('Server started on port: ' + port);
});
Step 02: Defining the routes

The next step is to define the routes for the microservices and then assign
each to a target in the controller. We have two endpoints. One endpoint
called "about" that returns information about the application. And a
"distance" endpoint that includes two path parameters, both Zip Codes of
the Lego store. This endpoint returns the distance, in miles, between
these two Zip Codes.

const controller = require('./controller');

[Link] = function(app) {
[Link]('/about')
.get([Link]);
[Link]('/distance/:zipcode1/:zipcode2')
.get([Link]);
};
Step 03: Adding Controller Logic

Within the controller file, we are going to create a controller object with
two properties. Those properties are the functions to handle the requests
we defined in the routes module.

const properties = require('../[Link]')

const distance = require('../service/distance');
const controllers = {
about: function(req, res) {
let aboutInfo = {
name: [Link],
version: [Link]
}
[Link](aboutInfo);
},
getDistance: function(req, res) {
[Link](req, res, function(err, dist) {
if (err)
[Link](err);
[Link](dist);
});
},
};

[Link] = controllers;

Q. How microservices communicate with

each other in [Link]?
ToDo

# 10. [Link] MIDDLEWARE

Q. What are the middleware functions in

[Link]?
Middleware functions are functions that have access to the request
object (req), the response object (res), and the next function in the
application's request-response cycle.

Middleware functions can perform the following tasks:

 Execute any code.

 Make changes to the request and the response objects.
 End the request-response cycle.
 Call the next middleware in the stack.

If the current middleware function does not end the request-response

cycle, it must call next() to pass control to the next middleware function.
Otherwise, the request will be left hanging.

The following figure shows the elements of a middleware function call:

Middleware functions that return a Promise will call next(value) when they
reject or throw an error. next will be called with either the rejected value
or the thrown Error.

Q. Explain the use of next in [Link]?

The next is a function in the Express router which executes the
middleware succeeding the current middleware.

Example:

To load the middleware function, call [Link](), specifying the middleware

function. For example, the following code loads
the myLogger middleware function before the route to the root path (/).

/**
* myLogger
*/
const express = require("express");
const app = express();

const myLogger = function (req, res, next) {

[Link]("LOGGED");
next();
};

[Link](myLogger);

[Link]("/", (req, res) => {

[Link]("Hello World!");
});

[Link](3000);

Note: The next() function is not a part of the [Link] or Express API, but is
the third argument that is passed to the middleware function.
The next() function could be named anything, but by convention it is
always named “next”. To avoid confusion, always use this convention.
Q. Why to use [Link]?
[Link] is a [Link] web application framework that provides broad
features for building web and mobile applications. It is used to build a
single page, multipage, and hybrid web application.

Features of [Link]:

 Fast Server-Side Development: The features of node js help

express saving a lot of time.
 Middleware: Middleware is a request handler that has access to
the application's request-response cycle.
 Routing: It refers to how an application's endpoint's URLs respond
to client requests.
 Templating: It provides templating engines to build dynamic
content on the web pages by creating HTML templates on the
server.
 Debugging: Express makes it easier as it identifies the exact part
where bugs are.

The [Link] framework makes it very easy to develop an application

which can be used to handle multiple types of requests like the GET, PUT,
and POST and DELETE requests.

Example:

/**
* Simple server using [Link]
*/
const express = require("express");
const app = express();

[Link]("/", function (req, res) {

[Link]("Hello World!");
});

const server = [Link](3000, function () {});

Q. Why should you separate Express 'app'

and 'server'?
Keeping the API declaration separated from the network related
configuration (port, protocol, etc) allows testing the API in-process,
without performing network calls, with all the benefits that it brings to the
table: fast testing execution and getting coverage metrics of the code. It
also allows deploying the same API under flexible and different network
conditions.

API declaration, should reside in [Link]:

/**
* [Link]
*/
const app = express();

[Link]([Link]());
[Link]("/api/events", [Link]);
[Link]("/api/forms", forms);
Server network declaration

/**
* [Link]
*/
const app = require('../app');
const http = require('http');

// Get port from environment and store in Express.

const port = normalizePort([Link] || '3000');
[Link]('port', port);

// Create HTTP server.

const server = [Link](app);

Q. What are some of the most popular

packages of [Link]?
Package Description
Async is a utility module which provides straight-forward, powerful
Async
functions for working with asynchronous JavaScript
Browserify will recursively analyze all the require() calls in your app in
Browserify order to build a bundle you can serve up to the browser in a
single <script> tag
Bower is a package manager for the web It works by fetching and
Bower installing packages from all over, taking care of hunting, finding,
downloading, and saving the stuff you're looking for
csv module has four sub modules which provides CSV generation,
Csv
parsing, transformation and serialization for [Link]
Debug is a tiny [Link] debugging utility modelled after node core's
Debug
debugging technique
Express Express is a fast, un-opinionated, minimalist web framework. It provides
 Package Description
small, robust tooling for HTTP servers, making it a great solution for
single page applications, web sites, hybrids, or public HTTP APIs
is a JavaScript Task Runner that facilitates creating new projects and
Grunt makes performing repetitive but necessary tasks such as linting, unit
testing, concatenating and minifying files (among other things) trivial
is a streaming build system that helps you automate painful or time-
Gulp
consuming tasks in your development workflow
is a streaming build system that helps you automate painful or time-
Hapi
consuming tasks in your development workflow
is a simple, zero-configuration command-line http server. It is powerful
Http-server enough for production usage, but it's simple and hackable enough to be
used for testing, local development, and learning
Inquirer A collection of common interactive command line user interfaces
Jquery jQuery is a fast, small, and feature-rich JavaScript library
Static analysis tool to detect errors and potential problems in JavaScript
Jshint
code and to enforce your team's coding conventions
Koa is web app framework. It is an expressive HTTP middleware for
Koa
[Link] to make web applications and APIs more enjoyable to write
The lodash library exported as a node module. Lodash is a modern
Lodash
JavaScript utility library delivering modularity, performance, & extras
Less The less library exported as a node module
A lightweight JavaScript date library for parsing, validating,
Moment
manipulating, and formatting dates
It is a MongoDB object modeling tool designed to work in an
Mongoose
asynchronous environment
The official MongoDB driver for [Link]. It provides a high-level API on
MongoDB
top of mongodb-core that is meant for end users
Npm is package manager for javascript
It is a simple monitor script for use during development of a [Link] app,
It will watch the files in the directory in which nodemon was started, and
Nodemon
if any files change, nodemon will automatically restart your node
application
Nodemaile
This module enables e-mail sending from a [Link] applications
r
Optimist is a [Link] library for option parsing with an argv hash
Phantomjs An NPM installer for PhantomJS, headless webkit with JS API. It has fast
 Package Description
and native support for various web standards: DOM handling, CSS
selector, JSON, Canvas, and SVG
A simple, unobtrusive authentication middleware for [Link]. Passport
uses the strategies to authenticate requests. Strategies can range from
Passport
verifying username and password credentials or authentication using
OAuth or OpenID
Q is a library for promises. A promise is an object that represents the
Q return value or the thrown exception that the function may eventually
provide
Request is Simplified HTTP request client make it possible to make http
Request
calls. It supports HTTPS and follows redirects by default
[Link] Its a [Link] realtime framework server
Sails is a API-driven framework for building realtime apps, using MVC
Sails
conventions (based on Express and [Link])
It enables simplified stream construction. It is easy way to create a stream
Through
that is both readable and writable
[Link] is a utility-belt library for JavaScript that provides support
Underscore for the usual functional suspects (each, map, reduce, filter...) without
extending any core JavaScript objects
Validator A nodejs module for a library of string validators and sanitizers
Winston A multi-transport async logging library for [Link]
A simple to use, blazing fast and thoroughly tested websocket client,
Ws
server and console for [Link]
Xml2js A Simple XML to JavaScript object converter
Yo A CLI tool for running Yeoman generators
Bindings for [Link] and [Link] to ZeroMQ. It is a high-performance
Zmq asynchronous messaging library, aimed at use in distributed or concurrent
applications

Q. How can you make sure your

dependencies are safe?
The only option is to automate the update / security audit of your
dependencies. For that there are free and paid options:

1. npm outdated
2. Trace by RisingStack
 3. NSP
4. GreenKeeper
5. Snyk
6. npm audit
7. npm audit fix

Q. What are the security mechanisms

available in [Link]?
1. Helmet module:

Helmet helps to secure your Express applications by setting various HTTP

headers, like:

 X-Frame-Options to mitigates clickjacking attacks,

 Strict-Transport-Security to keep your users on HTTPS,
 X-XSS-Protection to prevent reflected XSS attacks,
 X-DNS-Prefetch-Control to disable browsers DNS prefetching.

/**
* Helmet
*/
const express = require('express')
const helmet = require('helmet')
const app = express()

[Link](helmet())
2. JOI module:

Validating user input is one of the most important things to do when it

comes to the security of your application. Failing to do it correctly can
open up your application and users to a wide range of attacks, including
command injection, SQL injection or stored cross-site scripting.

To validate user input, one of the best libraries you can pick is joi. Joi is an
object schema description language and validator for JavaScript objects.

/**
* Joi
*/
const Joi = require('joi');

const schema = [Link]().keys({

username: [Link]().alphanum().min(3).max(30).required(),
password: [Link]().regex(/^[a-zA-Z0-9]{3,30}$/),
access_token: [[Link](), [Link]()],
birthyear: [Link]().integer().min(1900).max(2013),
email: [Link]().email()
}).with('username', 'birthyear').without('password', 'access_token')
// Return result
const result = [Link]({
username: 'abc',
birthyear: 1994
}, schema)
// [Link] === null -> valid
3. Regular Expressions:

Regular Expressions are a great way to manipulate texts and get the parts
that you need from them. However, there is an attack vector called
Regular Expression Denial of Service attack, which exposes the fact that
most Regular Expression implementations may reach extreme situations
for specially crafted input, that cause them to work extremely slowly.

The Regular Expressions that can do such a thing are commonly referred
as Evil Regexes. These expressions contain: *grouping with repetition,
*inside the repeated group: *repetition, or *alternation with overlapping

Examples of Evil Regular Expressions patterns:

(a+)+
([a-zA-Z]+)*
(a|aa)+
4. [Link]:

[Link] defines a standard to help organizations define the process

for security researchers to securely disclose security vulnerabilities.

const express = require('express')

const securityTxt = require('[Link]')

const app = express()

[Link]('/[Link]', securityTxt({
// your security address
contact: 'email@[Link]',
// your pgp key
encryption: 'encryption',
// if you have a hall of fame for securty resourcers, include the link
here
acknowledgements: '[Link]
}))

Q. What is npm in [Link]?

NPM stands for Node Package Manager. It provides following two main
functionalities.

 It works as an Online repository for [Link] packages/modules which

are present at <[Link]>.
  It works as Command line utility to install packages, do version
management and dependency management of [Link] packages.
NPM comes bundled along with [Link] installable. We can verify its
version using the following command-

npm --version
NPM helps to install any [Link] module using the following command.

npm install <Module Name>

For example, following is the command to install a famous [Link] web
framework module called express-

npm install express

Q. Why npm shrinkwrap is useful?

NPM shrinkwrap lets you lock down the versions of installed packages and
their descendant packages. It helps you use same package versions on all
environments (development, staging, production) and also improve
download and installation speed.

After installing packages using npm install or npm install <package-

name> and updating your node_modules folder, you should run

npm shrinkwrap
It should create new [Link] file with information about all
packages you use. Next time, when someone calls npm install, it will
install packages from [Link] and you will have the same
environment on all machines.

Q. How to handle file upload in [Link]?

File can be uploaded to the server using Multer module. Multer is a
[Link] middleware which is used for handling multipart/form-data, which
is mostly used library for uploading files.

1. Installing the dependencies:

npm install express body-parser multer --save

2. [Link]:

/**
* File Upload in [Link]
*/
const express = require("express");
const bodyParser = require("body-parser");
const multer = require("multer");
const app = express();
// for text/number data transfer between clientg and server
[Link](bodyParser());

const storage = [Link]({

destination: function (req, file, callback) {
callback(null, "./uploads");
},
filename: function (req, file, callback) {
callback(null, [Link] + "-" + [Link]());
},
});

const upload = multer({ storage: storage }).single("userPhoto");

[Link]("/", function (req, res) {

[Link](__dirname + "/[Link]");
});

// POST: upload for single file upload

[Link]("/api/photo", function (req, res) {
upload(req, res, function (err) {
if (err) {
return [Link]("Error uploading file.");
}
[Link]("File is uploaded");
});
});

[Link](3000, function () {
[Link]("Listening on port 3000");
});
3. [Link]:

<!DOCTYPE html>
<html lang="en">
<head>
<title>Multer-File-Upload</title>
</head>
<body>
<h1>MULTER File Upload | Single File Upload</h1>

<form id = "uploadForm"
enctype = "multipart/form-data"
action = "/api/photo"
method = "post"
>
<input type="file" name="userPhoto" />
<input type="submit" value="Upload Image" name="submit">
</form>
</body>
</html>

Q. Explain the terms body-parser, cookie-

parser, morgan, nodemon, pm2, serve-
favicon, cors, dotenv, fs-extra, moment in
[Link]?
1. body-parser:

body-parser extract the entire body portion of an incoming request stream

and exposes it on [Link]. The body-parser module parses the JSON,
buffer, string and URL encoded data submitted using HTTP POST request.

Example:

npm install body-parser

/**
* body-parser
*/
const express = require("express");
const bodyParser = require("body-parser");

const app = express();

// create application/json parser

const jsonParser = [Link]();

// create application/x-www-form-urlencoded parser

const urlencodedParser = [Link]({ extended: false });

// POST /login gets urlencoded bodies

[Link]("/login", urlencodedParser, function (req, res) {
[Link]("welcome, " + [Link]);
});

// POST /api/users gets JSON bodies

[Link]("/api/users", jsonParser, function (req, res) {
// create user in [Link]
});
2. cookie-parser:

A cookie is a piece of data that is sent to the client-side with a request and
is stored on the client-side itself by the Web Browser the user is currently
using.

The cookie-parser middleware's cookieParser function takes a secret string

or array of strings as the first argument and an options object as the
second argument.

Installation:

npm install cookie-parser

Example:

/**
* cookie-parser
*/
const express = require('express')
const cookieParser = require('cookie-parser')

const app = express()

[Link](cookieParser())

[Link]('/', function (req, res) {

// Cookies that have not been signed
[Link]('Cookies: ', [Link])

// Cookies that have been signed

[Link]('Signed Cookies: ', [Link])
})

[Link](3000)
3. morgan:

HTTP request logger middleware for [Link].

Installation:

npm install morgan

Example:

/**
* Writing logs to a file
*/
const express = require('express')
const fs = require('fs')
const morgan = require('morgan')
const path = require('path')

const app = express()

// create a write stream (in append mode)

const accessLogStream = [Link]([Link](__dirname,
'[Link]'), { flags: 'a' })

// setup the logger

[Link](morgan('combined', { stream: accessLogStream }))

[Link]('/', function (req, res) {

[Link]('hello, world!')
})
4. nodemon:

Nodemon is a utility that will monitor for any changes in source and
automatically restart your server.

Installation:

npm install -g nodemon

Example:

{
// ...
"scripts": {
"start": "nodemon [Link]"
 },
// ...
}
5. pm2:

P(rocess) M(anager) 2 (pm2) is a production process manager for [Link]

applications with a built-in load balancer. It allows to keep applications
alive forever, to reload them without downtime and to facilitate common
system admin tasks.

Installation:

npm install pm2 -g

Start an application:

pm2 start [Link]

Reference:

 [Link]

6. serve-favicon:

[Link] middleware for serving a favicon. It create new middleware to

serve a favicon from the given path to a favicon file. path may also be a
Buffer of the icon to serve.

Installation:

npm install serve-favicon

Example:

/**
* serve-favicon
*/
const express = require('express')
const favicon = require('serve-favicon')
const path = require('path')

const app = express()

[Link](favicon([Link](__dirname, 'public', '[Link]')))

// Add your routes here, etc.

[Link](3000)
7. cors:

Cross-Origin Resource Sharing (CORS) headers allow apps running in the

browser to make requests to servers on different domains (also known as
origins). CORS headers are set on the server side - the HTTP server is
responsible for indicating that a given HTTP request can be cross-origin.

Installation:
npm install cors
Example:

/**
* Enable CORS for a Single Route
*/
const express = require('express')
const cors = require('cors')
const app = express()

[Link]('/products/:id', cors(), function (req, res, next) {

[Link]({msg: 'This is CORS-enabled for a Single Route'})
})

[Link](8080, function () {
[Link]('CORS-enabled web server listening on port 80')
})
8. dotenv:

When a NodeJs application runs, it injects a global variable

called [Link] which contains information about the state of
environment in which the application is running. The dotenv loads
environment variables stored in the .env file into [Link].

Installation:

npm install dotenv

Usage:

// .env

DB_HOST=localhost
DB_USER=admin
DB_PASS=root
/**
* [Link]
*/
const db = require('db')

[Link]({
host: [Link].DB_HOST,
username: [Link].DB_USER,
password: [Link].DB_PASS
})
9. fs-extra:

fs-extracontains methods that aren't included in the vanilla [Link] fs

package. Such as recursive mkdir, copy, and remove. It also uses graceful-fs
to prevent EMFILE errors.

Installation:

npm install fs-extra

Usage:

/**
 * fs-extra
*/
const fs = require('fs-extra')

// Async with callbacks:

[Link]('/tmp/myfile', '/tmp/mynewfile', err => {
if (err) return [Link](err)
[Link]('success!')
})
10. moment:

A JavaScript date library for parsing, validating, manipulating, and

formatting dates.

Installation:

npm install moment --save

Usage:

 Format Dates

const moment = require('moment');

moment().format('MMMM Do YYYY, h:mm:ss a'); // October 24th 2022, 3:15:22

pm
moment().format('dddd'); // Saturday
moment().format("MMM Do YY"); // Oct 24th 22

 Relative Time

const moment = require('moment');

moment("20111031", "YYYYMMDD").fromNow(); // 9 years ago

moment("20120620", "YYYYMMDD").fromNow(); // 8 years ago
moment().startOf('day').fromNow(); // 15 hours ago

 Calendar Time

const moment = require('moment');

moment().subtract(10, 'days').calendar(); // 10/14/2022

moment().subtract(6, 'days').calendar(); // Last Sunday at 3:18 PM
moment().subtract(3, 'days').calendar(); // Last Wednesday at 3:18 PM

# 11. [Link] RESTFUL API

Q. Explain RESTful Web Services in [Link]?

REST stands for REpresentational State Transfer. REST is web standards
based architecture and uses HTTP Protocol. It is an architectural style as
well as an approach for communications purposes that is often used in
various web services development. A REST Server simply provides access
to resources and REST client accesses and modifies the resources using
HTTP protocol.

HTTP methods:

 GET − Provides read-only access to a resource.

 PUT − Updates an existing resource or creates a new resource.
 DELETE − Removes a resource.
 POST − Creates a new resource.
 PATCH− Update/modify a resource

Example:

// [Link]
{
"user1" : {
"id": 1,
"name" : "Ehsan Philip",
"age" : 24
},

"user2" : {
"id": 2,
"name" : "Karim Jimenez",
"age" : 22
},

"user3" : {
"id": 3,
"name" : "Giacomo Weir",
"age" : 18
}
}
List Users ( GET method)

Let's implement our first RESTful API listUsers using the following code in
a [Link] file −

const express = require('express');

const app = express();
const fs = require("fs");

[Link]('/listUsers', function (req, res) {

[Link]( __dirname + "/" + "[Link]", 'utf8', function (err,
data) {
[Link]( data );
[Link]( data );
});
})

const server = [Link](3000, function () {

const host = [Link]().address
const port = [Link]().port
[Link]("App listening at [Link] host, port)
});
Add User ( POST method )

Following API will show you how to add new user in the list.

const express = require('express');

const app = express();
const fs = require("fs");

const user = {
"user4" : {
"id": 4,
"name" : "Spencer Amos",
"age" : 28
}
}

[Link]('/addUser', function (req, res) {

// First read existing users.
[Link]( __dirname + "/" + "[Link]", 'utf8', function (err,
data) {
data = [Link]( data );
data["user4"] = user["user4"];
[Link]( data );
[Link]( [Link](data));
});
})

const server = [Link](3000, function () {

const host = [Link]().address
const port = [Link]().port
[Link]("App listening at [Link] host, port)
})
Delete User:

const express = require('express');

const app = express();
const fs = require("fs");

const id = 2;

[Link]('/deleteUser', function (req, res) {

// First read existing users.
[Link]( __dirname + "/" + "[Link]", 'utf8', function (err,
data) {
data = [Link]( data );
delete data["user" + 2];
[Link]( data );
[Link]( [Link](data));
});
})

const server = [Link](3000, function () {

const host = [Link]().address
const port = [Link]().port
[Link]("App listening at [Link] host, port)
})
Q. What is the difference between
[Link] and [Link]?
The [Link] are a part of a path in URL and they're also known as
URL variables. for example, if you have the route /books/:id, then
the id property will be available as [Link]. [Link] default
value is an empty object {}.

A [Link] is a part of a URL that assigns values to specified

parameters. A query string commonly includes fields added to a base URL
by a Web browser or other client application, for example as part of an
HTML form. A query is the last part of URL

Example 01: [Link]

/**
* [Link]
*/

// GET [Link]

[Link]('/employees/:id', (req, res, next) => {

[Link]([Link]); // 10
})
Example 02: [Link]

/**
* [Link]
*/

// GET [Link]

[Link]('/employees', (req, res, next) => {

[Link]([Link]) // 20
})

Q. How to make post request in [Link]?

Following code snippet can be used to make a Post Request in [Link].

/**
* POST Request
*/
const request = require("request");

[Link]("[Link] { form: { key: "value" } },

function (error, response, body) {
if (!error && [Link] === 200) {
[Link](body);
}
}
);
Q. What are Promises in [Link]?
It allows to associate handlers to an asynchronous action's eventual
success value or failure reason. This lets asynchronous methods return
values like synchronous methods: instead of the final value, the
asynchronous method returns a promise for the value at some point in the
future.

Promises in [Link] promised to do some work and then had separate

callbacks that would be executed for success and failure as well as
handling timeouts. Another way to think of promises in [Link] was that
they were emitters that could emit only two events: success and [Link]
cool thing about promises is you can combine them into dependency
chains (do Promise C only when Promise A and Promise B complete).

The core idea behind promises is that a promise represents the result of
an asynchronous operation. A promise is in one of three different states:

 pending - The initial state of a promise.

 fulfilled - The state of a promise representing a successful operation.
 rejected - The state of a promise representing a failed operation.
Once a promise is fulfilled or rejected, it is immutable (i.e. it can
never change again).

Creating a Promise:

const myPromise = new Promise(function(resolve, reject){

....
})

Q. How can you secure your HTTP cookies

against XSS attacks?
1. When the web server sets cookies, it can provide some additional
attributes to make sure the cookies won't be accessible by using malicious
JavaScript. One such attribute is HttpOnly.

Set-Cookie: [name]=[value]; HttpOnly

HttpOnly makes sure the cookies will be submitted only to the domain
they originated from.

2. The "Secure" attribute can make sure the cookies are sent over
secured channel only.

Set-Cookie: [name]=[value]; Secure

3. The web server can use X-XSS-Protection response header to make
sure pages do not load when they detect reflected cross-site scripting
(XSS) attacks.
X-XSS-Protection: 1; mode=block
4. The web server can use HTTP Content-Security-Policy response header
to control what resources a user agent is allowed to load for a certain
page. It can help to prevent various types of attacks like Cross Site
Scripting (XSS) and data injection attacks.

Content-Security-Policy: default-src 'self' *.[Link]

Q. How to make an HTTP POST request

using [Link]?
const https = require('https')

const obj = {
"userId":1,
"id":1,
"title":"whatever",
"completed":false
}

const data = [Link](obj)

const options = {
hostname: '[Link]',
port: 443,
path: '/todos',
method: 'POST',
headers: {
'Content-Type': 'application/json',
'Content-Length': [Link]
}
}

const req = [Link](options, res => {

[Link](`statusCode: ${[Link]}`)

[Link]('data', d => {
[Link](d)
})
})

[Link]('error', error => {

[Link](error)
})

[Link](data)
[Link]()

Q. What is asynchronous programming in

[Link]?
Asynchronous programming is a form of parallel programming that allows
a unit of work to run separately from the primary application thread.
When the work is complete, it notifies the main thread (as well as whether
the work was completed or failed). There are numerous benefits to using
it, such as improved application performance and enhanced
responsiveness.

Q. What is the difference between

Asynchronous and Non-blocking?
1. Asynchronous:

The architecture of asynchronous explains that the message sent will not
give the reply on immediate basis just like we send the mail but do not
get the reply on an immediate basis. It does not have any dependency or
order. Hence improving the system efficiency and performance. The
server stores the information and when the action is done it will be
notified.

2. Non-Blocking:

Nonblocking immediately responses with whatever data available.

Moreover, it does not block any execution and keeps on running as per
the requests. If an answer could not be retrieved then in those cases API
returns immediately with an error. Nonblocking is mostly used with
I/O(input/output). [Link] is itself based on nonblocking I/O model. There
are few ways of communication that a nonblocking I/O has completed. The
callback function is to be called when the operation is completed.
Nonblocking call uses the help of javascript which provides a callback
function.

Q. How [Link] prevents blocking code?

Blocking vs Non-blocking:

Blocking is when the execution of additional JavaScript in the [Link]

process must wait until a non-JavaScript operation completes. This
happens because the event loop is unable to continue running JavaScript
while a blocking operation is occurring.

Synchronous methods in the [Link] standard library that use libuv are
the most commonly used blocking operations. Native modules may also
have blocking methods. Blocking methods execute synchronously and non-
blocking methods execute asynchronously.
Example:

// Blocking
const fs = require('fs');
const data = [Link]('/[Link]'); // blocks here until file is read
[Link](data);
moreWork(); // will run after [Link]

// Non-blocking
const fs = require('fs');
[Link]('/[Link]', (err, data) => {
if (err) throw err;
[Link](data);
});
moreWork(); // will run before [Link]

Q. Name the types of API functions in

[Link]?
There are two types of API functions in [Link]:

 Asynchronous, Non-blocking functions

 Synchronous, Blocking functions

1. Blocking functions:

In a blocking operation, all other code is blocked from executing until an

I/O event that is being waited on occurs. Blocking functions execute
synchronously.

Example:

const fs = require('fs');
const data = [Link]('/[Link]'); // blocks here until file is read
[Link](data);
// moreWork(); will run after [Link]
The second line of code blocks the execution of additional JavaScript until
the entire file is read. moreWork () will only be called after [Link]

2. Non-blocking functions:

In a non-blocking operation, multiple I/O calls can be performed without

the execution of the program being halted. Non-blocking functions
execute asynchronously.

Example:

const fs = require('fs');
[Link]('/[Link]', (err, data) => {
if (err) throw err;
[Link](data);
});
// moreWork(); will run before [Link]
Since [Link]() is non-blocking, moreWork() does not have to wait for
the file read to complete before being called. This allows for higher
throughput.

Q. What is difference between put and

patch?
PUT and PATCH are HTTP verbs and they both relate to updating a
resource. The main difference between PUT and PATCH requests are in
the way the server processes the enclosed entity to modify the resource
identified by the Request-URI.

In a PUT request, the enclosed entity is considered to be a modified

version of the resource stored on the origin server, and the client is
requesting that the stored version be replaced.

With PATCH, however, the enclosed entity contains a set of instructions

describing how a resource currently residing on the origin server should
be modified to produce a new version.

Also, another difference is that when you want to update a resource with
PUT request, you have to send the full payload as the request whereas
with PATCH, you only send the parameters which you want to update.

The most commonly used HTTP verbs POST, GET, PUT, DELETE are similar
to CRUD (Create, Read, Update and Delete) operations in database. We
specify these HTTP verbs in the capital case. So, the below is the
comparison between them.

 POST - create
 GET - read
 PUT - update
 DELETE - delete

PATCH: Submits a partial modification to a resource. If you only need to

update one field for the resource, you may want to use the PATCH
method.

Q. List types of Http requests supported by

[Link]?
The HTTP core module is a key module to [Link] networking.
const http = require('http')
[Link]

require('http').METHODS
[ 'ACL',
'BIND',
'CHECKOUT',
'CONNECT',
'COPY',
'DELETE',
'GET',
'HEAD',
'LINK',
'LOCK',
'M-SEARCH',
'MERGE',
'MKACTIVITY',
'MKCALENDAR',
'MKCOL',
'MOVE',
'NOTIFY',
'OPTIONS',
'PATCH',
'POST',
'PROPFIND',
'PROPPATCH',
'PURGE',
'PUT',
'REBIND',
'REPORT',
'SEARCH',
'SUBSCRIBE',
'TRACE',
'UNBIND',
'UNLINK',
'UNLOCK',
'UNSUBSCRIBE' ]
http.STATUS_CODES

require('http').STATUS_CODES
{ '100': 'Continue',
'101': 'Switching Protocols',
'102': 'Processing',
'200': 'OK',
'201': 'Created',
'202': 'Accepted',
'203': 'Non-Authoritative Information',
'204': 'No Content',
'205': 'Reset Content',
'206': 'Partial Content',
'207': 'Multi-Status',
'208': 'Already Reported',
'226': 'IM Used',
'300': 'Multiple Choices',
'301': 'Moved Permanently',
'302': 'Found',
'303': 'See Other',
'304': 'Not Modified',
'305': 'Use Proxy',
'307': 'Temporary Redirect',
'308': 'Permanent Redirect',
'400': 'Bad Request',
'401': 'Unauthorized',
'402': 'Payment Required',
'403': 'Forbidden',
'404': 'Not Found',
'405': 'Method Not Allowed',
'406': 'Not Acceptable',
'407': 'Proxy Authentication Required',
'408': 'Request Timeout',
'409': 'Conflict',
'410': 'Gone',
'411': 'Length Required',
'412': 'Precondition Failed',
'413': 'Payload Too Large',
'414': 'URI Too Long',
'415': 'Unsupported Media Type',
'416': 'Range Not Satisfiable',
'417': 'Expectation Failed',
'418': 'I\'m a teapot',
'421': 'Misdirected Request',
'422': 'Unprocessable Entity',
'423': 'Locked',
'424': 'Failed Dependency',
'425': 'Unordered Collection',
'426': 'Upgrade Required',
'428': 'Precondition Required',
'429': 'Too Many Requests',
'431': 'Request Header Fields Too Large',
'451': 'Unavailable For Legal Reasons',
'500': 'Internal Server Error',
'501': 'Not Implemented',
'502': 'Bad Gateway',
'503': 'Service Unavailable',
'504': 'Gateway Timeout',
'505': 'HTTP Version Not Supported',
'506': 'Variant Also Negotiates',
'507': 'Insufficient Storage',
'508': 'Loop Detected',
'509': 'Bandwidth Limit Exceeded',
'510': 'Not Extended',
'511': 'Network Authentication Required' }
Making HTTP Requests

const request = require('request');

request('[Link] function(err, res, body) {

[Link](body);
});
The first argument to request can either be a URL string, or an object of
options. Here are some of the more common options you'll encounter in
your applications:

 url: The destination URL of the HTTP request

 method: The HTTP method to be used (GET, POST, DELETE, etc)
 headers: An object of HTTP headers (key-value) to be set in the
request
 form: An object containing key-value form data
const request = require('request');

const options = {
url: '[Link]
method: 'GET',
headers: {
'Accept': 'application/json',
'Accept-Charset': 'utf-8',
'User-Agent': 'my-reddit-client'
}
};

request(options, function(err, res, body) {

let json = [Link](body);
[Link](json);
});
Using the options object, this request uses the GET method to retrieve
JSON data directly from Reddit, which is returned as a string in the body
field. From here, you can use [Link] and use the data as a normal
JavaScript object.

Q. What is difference between promises and

async-await in [Link]?
1. Promises:

A promise is used to handle the asynchronous result of an operation.

JavaScript is designed to not wait for an asynchronous block of code to
completely execute before other synchronous parts of the code can run.
With Promises, we can defer the execution of a code block until an async
request is completed. This way, other operations can keep running
without interruption.

States of Promises:

 Pending: Initial State, before the Promise succeeds or fails.

 Resolved: Completed Promise
 Rejected: Failed Promise, throw an error

Example:

function logFetch(url) {
return fetch(url)
.then(response => {
[Link](response);
})
.catch(err => {
[Link]('fetch failed', err);
});
}
2. Async-Await:
Awaitis basically syntactic sugar for Promises. It makes asynchronous
code look more like synchronous/procedural code, which is easier for
humans to understand.

Putting the keyword async before a function tells the function to return a
Promise. If the code returns something that is not a Promise, then
JavaScript automatically wraps it into a resolved promise with that value.
The await keyword simply makes JavaScript wait until that Promise settles
and then returns its result.

Example:

async function logFetch(url) {

try {
const response = await fetch(url);
[Link](response);
}
catch (err) {
[Link]('fetch failed', err);
}
}

Q. Mention the steps by which you can

async in [Link]?
ES 2017 introduced Asynchronous functions. Async functions are
essentially a cleaner way to work with asynchronous code in JavaScript.

1. Async/Await:

 The newest way to write asynchronous code in JavaScript.

 It is non blocking (just like promises and callbacks).
 Async/Await was created to simplify the process of working with and
writing chained promises.
 Async functions return a Promise. If the function throws an error, the
Promise will be rejected. If the function returns a value, the Promise
will be resolved.

Syntax

// Normal Function
function add(x,y){
return x + y;
}
// Async Function
async function add(x,y){
return x + y;
}
2. Await:
Async functions can make use of the await expression. This will pause the
async function and wait for the Promise to resolve prior to moving on.

Example:

function doubleAfter2Seconds(x) {
return new Promise(resolve => {
setTimeout(() => {
resolve(x * 2);
}, 2000);
});
}

async function addAsync(x) {

const a = await doubleAfter2Seconds(10);
const b = await doubleAfter2Seconds(20);
const c = await doubleAfter2Seconds(30);
return x + a + b + c;
}

addAsync(10).then((sum) => {
[Link](sum);
});

Q. How to use Q promise in [Link]?

A promise is an object that represents the return value or the thrown
exception that the function may eventually provide. A promise can also be
used as a proxy for a remote object to overcome latency.

Promise is relatively an easy implementation for asynchronous operation.

The promise object returned from the function represents an operation
which is not completed yet, but it guarantees to the caller of the operation
that the operation will be completed in future.

Promise has the following states:

 Pending - asynchronous operation is not yet completed.

 Fulfilled - asynchronous operation is completed successfully.
 Rejected - asynchronous operation is terminated with an error.
 Settled - asynchronous operation is either fulfilled or rejected.
 Callback - function is executed if the promise is executed with
value.
 Errback - function is executed if the promise is rejected.

Moving to Promises from Callback

On the first pass, promises can mitigate the Pyramid of Doom: the
situation where code marches to the right faster than it marches forward.
step1(function (value1) {
step2(value1, function(value2) {
step3(value2, function(value3) {
step4(value3, function(value4) {
// Do something with value4
});
});
});
});
With a promise library, it can flatten the pyramid.

[Link](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();
Reference:

 [Link]

Q. What are async functions in Node?

Q. How do you convert an existing callback API to promises?

ToDo

# 12. [Link] ROUTING

Q. How does routing work in [Link]?

Routing defines the way in which the client requests are handled by the
application endpoints. We define routing using methods of the Express
app object that correspond to HTTP methods; for example, [Link]() to
handle GET requests and [Link] to handle POST requests, [Link]() to
handle all HTTP methods and [Link]() to specify middleware as the
callback function.

These routing methods "listens" for requests that match the specified
route(s) and method(s), and when it detects a match, it calls the specified
callback function.
Syntax:

[Link](PATH, HANDLER)
Where:

 app is an instance of express.

 METHOD is an HTTP request method.
 PATH is a path on the server.
 HANDLER is the function executed when the route is matched.

a) Route methods:

// GET method route

[Link]('/', function (req, res) {
[Link]('GET request')
})

// POST method route

[Link]('/login', function (req, res) {
[Link]('POST request')
})

// ALL method route

[Link]('/secret', function (req, res, next) {
[Link]('Accessing the secret section ...')
next() // pass control to the next handler
})
b) Route paths:

Route paths, in combination with a request method, define the endpoints

at which requests can be made. Route paths can be strings, string
patterns, or regular expressions.

The characters ?, +, *, and () are subsets of their regular expression

counterparts. The hyphen (-) and the dot (.) are interpreted literally by
string-based paths.

Example:

// This route path will match requests to /about.

[Link]('/about', function (req, res) {
[Link]('about')
})

// This route path will match acd and abcd.

[Link]('/ab?cd', function (req, res) {
[Link]('ab?cd')
})

// This route path will match butterfly and dragonfly

[Link](/.*fly$/, function (req, res) {
[Link]('/.*fly$/')
})
c) Route parameters:

Route parameters are named URL segments that are used to capture the
values specified at their position in the URL. The captured values are
populated in the [Link] object, with the name of the route parameter
specified in the path as their respective keys.

Example:

[Link]('/users/:userId', function (req, res) {

[Link]([Link])
})
Response methods:

Method Description
[Link]() Prompt a file to be downloaded.
[Link]() End the response process.
[Link]() Send a JSON response.
[Link]() Send a JSON response with JSONP support.
[Link]() Redirect a request.
[Link]() Render a view template.
[Link]() Send a response of various types.
[Link]() Send a file as an octet stream.

[Link]()
Set the response status code and send its string representation as
the response body.
d) Router method:

const express = require('express')

const router = [Link]()

// middleware that is specific to this router

[Link](function timeLog (req, res, next) {
[Link]('Time: ', [Link]())
next()
})

// define the home page route

[Link]('/', function (req, res) {
[Link]('Birds home page')
})

// define the about route

[Link]('/about', function (req, res) {
[Link]('About birds')
})

[Link] = router
# 13. [Link] CACHING

# 14. [Link] ERROR HANDLING

Q. What is the preferred method of

resolving unhandled exceptions in [Link]?
Unhandled exceptions in [Link] can be caught at the Process level by
attaching a handler for uncaughtException event.

[Link]('uncaughtException', function(err) {
[Link]('Caught exception: ' + err);
});
Process is a global object that provides information about the current
[Link] process. Process is a listener function that is always listening to
events.

Few events are :

1. Exit
2. disconnect
3. unhandledException
4. rejectionHandled

Q. Explain Error Handling approaches in [Link]?

Q. How would you handle errors for async code in [Link]?

Q. How to solve "Process out of Memory Exception" in [Link]?

Q. What are the types of memory leaks in [Link]

# 15. [Link] LOGGING

Q. How to debug an application in [Link]?

1. node-inspector:

npm install -g node-inspector

Run

node-debug [Link]
2. Debugging:

 Debugger
 Node Inspector
 Visual Studio Code
 Cloud9
 Brackets

3. Profiling:

1. node --prof ./[Link]

2. node --prof-process ./the-generated-log-file
4. Heapdumps:

 node-heapdump with Chrome Developer Tools

5. Tracing:

 Interactive Stack Traces with TraceGL

6. Logging:

Libraries that output debugging information

 Caterpillar
 Tracer
 scribbles

Libraries that enhance stack trace information

 Longjohn

# 16. [Link] INTERNATIONALIZATION

Q. How to use locale (i18n) in [Link]?

# 17. [Link] TESTING

Q. What is a stub?
Stubbing and verification for [Link] tests. Enables you to validate and
override behaviour of nested pieces of code such as methods, require()
and npm modules or even instances of classes. This library is inspired on
node-gently, MockJS and mock-require.

Features of Stub:

 Produces simple, lightweight Objects capable of extending down

their tree
 Compatible with Nodejs
 Easily extendable directly or through an ExtensionManager
 Comes with predefined, usable extensions

Stubs are functions/programs that simulate the behaviours of

components/modules. Stubs provide canned answers to function calls
made during test cases. Also, you can assert on with what these stubs
were called.

A use-case can be a file read, when you do not want to read an actual file:

const fs = require('fs');

const readFileStub = [Link](fs, 'readFile', function (path, cb) {

return cb(null, 'filecontent');
});

expect(readFileStub).[Link];
[Link]();

Q. What is a test pyramid?

The "Test Pyramid" is a metaphor that tells us to group software tests into
buckets of different granularity. It also gives an idea of how many tests we
should have in each of these groups. It shows which kinds of tests you
should be looking for in the different levels of the pyramid and gives
practical examples on how these can be implemented.
Mike Cohn's original test pyramid consists of three layers that your test
suite should consist of (bottom to top):

1. Unit Tests
2. Service Tests
3. User Interface Tests

Q. How to use Joi module for schema

validation in [Link]?
Joi module is a popular module for data validation. This module validates
the data based on schemas. There are various functions like optional(),
required(), min(), max(), etc which make it easy to use and a user-friendly
module for validating the data.

Example:

const Joi = require("joi");

// User-defined function to validate the user

function validateUser(user) {

const JoiSchema = [Link]({

username: [Link]().min(5).max(30).required(),

email: [Link]().email().min(5).max(50).optional(),

date_of_birth: [Link]().optional(),

account_status: [Link]()
.valid("activated")
.valid("unactivated")
.optional(),
}).options({ abortEarly: false });
 return [Link](user);
}

const user = {
username: "Deepak Lucky",
email: "[Link]@[Link]",
date_of_birth: "2000-07-07",
account_status: "activated",
};

let response = validateUser(user);

if ([Link]) {
[Link]([Link]);
} else {
[Link]("Validated Data");
}

# 18. [Link] MISCELLANEOUS

Q. What is crypto in [Link]?

The [Link] Crypto module supports cryptography. It provides
cryptographic functionality that includes a set of wrappers for open SSL's
hash HMAC, cipher, decipher, sign and verify functions.

 Hash: A hash is a fixed-length string of bits i.e. procedurally and

deterministically generated from some arbitrary block of source
data.
 HMAC: HMAC stands for Hash-based Message Authentication Code.
It is a process for applying a hash algorithm to both data and a
secret key that results in a single final hash.
 Encryption Example using Hash and HMAC

const crypto = require('crypto');

const secret = 'abcdefg';
const hash = [Link]('sha256', secret)
.update('Welcome to [Link]')
.digest('hex');
[Link](hash);

 Encryption example using Cipher

const crypto = require('crypto');

const cipher = [Link]('aes192', 'a password');

const encrypted = [Link]('Hello [Link]', 'utf8', 'hex');

encrypted += [Link]('hex');
[Link](encrypted);

 Decryption example using Decipher

const crypto = require('crypto');

const decipher = [Link]('aes192', 'a password');

const encrypted =
'4ce3b761d58398aed30d5af898a0656a3174d9c7d7502e781e83cf6b9fb836d5';
const decrypted = [Link](encrypted, 'hex', 'utf8');
decrypted += [Link]('utf8');

[Link](decrypted);

Q. How to execute an external program

from within [Link]?
const { exec } = require('child_process');

exec('"/path/to/test file/[Link]" arg1 arg2');

exec('echo "The \\$HOME variable is $HOME"');

Q. What is REPL?
REPL (READ, EVAL, PRINT, LOOP) is a computer environment similar to
Shell (Unix/Linux) and command prompt. Node comes with the REPL
environment when it is installed. System interacts with the user through
outputs of commands/expressions used. It is useful in writing and
debugging the codes. The work of REPL can be understood from its full
form:

 Read: It reads the inputs from users and parses it into JavaScript
data structure. It is then stored to memory.
 Eval: The parsed JavaScript data structure is evaluated for the
results.
 Print: The result is printed after the evaluation.
 Loop: Loops the input command. To come out of NODE REPL, press
ctrl+c twice

Simple Expression

$ node
> 10 + 20
30
> 10 + ( 20 * 30 ) - 40
570
>
Q. What does the runtime environment
mean in [Link]?
The [Link] runtime is the software stack responsible for installing your
web service's code and its dependencies and running your service.

The [Link] runtime for App Engine in the standard environment is

declared in the [Link] file:

runtime: nodejs10
The runtime environment is literally just the environment your application
is running in. This can be used to describe both the hardware and the
software that is running your application. How much RAM, what version of
node, what operating system, how much CPU cores, can all be referenced
when talking about a runtime environment.

Q. Explain usage of NODE_ENV?

NODE_ENV is an environment variable made popular by the express web
server framework. When a node application is run, it can check the value
of the environment variable and do different things based on the value.

For example, when we work on a project and there are production and
development environments. We don't need to use caching in the
development env. So we set

NODE_ENV=development
and use the code below

if ([Link].NODE_ENV === 'development')

useCaching = false;
Upon that, if the project runs on production it will use caching.

Q. How assert works in [Link]?

The assert module provides a way of testing expressions. If the expression
evaluates to 0, or false, an assertion failure is being caused, and the
program is terminated.

This module was built to be used internally by [Link].

// Sample usage

const assert = require('assert');

assert(50 > 70, "50 is less than 70.");
Q. What is the use of DNS module in
[Link]?
DNS is a node module used to do name resolution facility which is
provided by the operating system as well as used to do an actual DNS
lookup. No need for memorising IP addresses – DNS servers provide a
nifty solution of converting domain or subdomain names to IP addresses.
This module provides an asynchronous network wrapper and can be
imported using the following syntax.

const dns = require('dns');

Example: [Link]() function

const dns = require('dns');

[Link]('[Link]', (err, addresses, family) => {
[Link]('addresses:', addresses);
[Link]('family:',family);
});
Example: resolve4() and reverse() functions

const dns = require('dns');

dns.resolve4('[Link]', (err, addresses) => {
if (err) throw err;
[Link](`addresses: ${[Link](addresses)}`);
[Link]((a) => {
[Link](a, (err, hostnames) => {
if (err) {
throw err;
}
[Link](`reverse for ${a}: ${[Link](hostnames)}`);
});
});
});
Example: Print the localhost name using lookupService() function

const dns = require('dns');

[Link]('[Link]', 22, (err, hostname, service) => {
[Link](hostname, service);
// Prints: localhost
});

Q. What is JIT and how is it related to

[Link]?
[Link] has depended on the V8 JavaScript engine to provide code
execution in the language. The V8 is a JavaScript engine built at the
google development center, in Germany. It is open source and written in
C++. It is used for both client side (Google Chrome) and server side
([Link]) JavaScript applications. A central piece of the V8 engine that
allows it to execute JavaScript at high speed is the JIT (Just In Time)
compiler. This is a dynamic compiler that can optimize code during
runtime. When V8 was first built the JIT Compiler was dubbed
FullCodegen. Then, the V8 team implemented Crankshaft, which included
many performance optimizations that FullCodegen did not implement.

The V8 was first designed to increase the performance of the JavaScript

execution inside web browsers. In order to obtain speed, V8 translates
JavaScript code into more efficient machine code instead of using an
interpreter. It compiles JavaScript code into machine code at execution by
implementing a JIT (Just-In-Time) compiler like a lot of modern JavaScript
engines such as SpiderMonkey or Rhino (Mozilla) are doing. The main
difference with V8 is that it doesn't produce bytecode or any intermediate
code.

Q. How to access cache data in [Link] ?

ToDo

Q. How to implement caching in [Link]

using Redis?
ToDo

Q. How to implement Memcached in

[Link]?
Memcached is a general-purpose distributed memory caching system. It
is often used to speed up dynamic database-driven websites by caching
data and objects in RAM to reduce the number of times an external data
source (such as a database or API) must be read. Memcached is free and
open-source software, licensed under the Revised BSD licence.
Memcached runs on Unix-like operating systems (at least LINUX and OS X)
and on Microsoft windows.

We can store data to memcached server in key pair format. So whenever

any request come from the app can be matched with memcached server
without any query from mysql/Nosql server. This increases the
performance of the application.

Installation:
npm install memcached
Setting up the client:

The constructor of the memcached client take 2 different arguments

server locations and options. Syntax:

const Memcached = require('memcached');

const memcached = new Memcached(Server locations, options);
Example:

/**
* Memcached
*/
const Memcached = require('memcached');
// all global configurations should be applied to the .config object of the
Client.
[Link] = 25;

const memcached = new Memcached('localhost:11211', { retries:10,

retry:10000, remove:true, failOverServers:['[Link]:11211']});

Q. How to generate and verify checksum of

the given string in Nodejs
The checksum (aka hash sum) calculation is a one-way process of
mapping an extensive data set of variable length (e.g., message, file), to a
smaller data set of a fixed length (hash). The length depends on a hashing
algorithm.

For the checksum generation, we can use node crypto() module. The
module uses createHash(algorithm) to create a checksum (hash) generator.
The algorithm is dependent on the available algorithms supported by the
version of OpenSSL on the platform.

Example:

const crypto = require('crypto');

// To get a list of all available hash algorithms

[Link]() // [ 'md5', 'sha1', 'sha3-256', ... ]

// Create hash of SHA1 type

const key = "MY_SECRET_KEY";

// 'digest' is the output of hash function containing

// only hexadecimal digits
hashPwd = [Link]('sha1').update(key).digest('hex');

[Link](hashPwd); //ef5225a03e4f9cc953ab3c4dd41f5c4db7dc2e5b