Top 4 JavaScript Concepts a Node.js Beginner Must Know

DZone 's Guide to

Top 4 JavaScript Concepts a Node.js Beginner Must Know

Wouldn’t it be awesome if you had to know only one programming language for building a full stack application. Ryan Dahl put this thought into action and created Node.js. Here are the four basic concepts of it that you should put into practice.

· Web Dev Zone ·
Free Resource

Wouldn’t it be awesome if you had to know only one programming language for building a full stack application. Ryan Dahl put this thought into action and created Node.js. Node.js is a server-side framework that is built upon Chrome’s powerful V8 JavaScript engine. Although originally written in C++, applications are run through JavaScript.

See, problem solved. One language to rule them all. But this also brings you down to the fact that now your whole application is using the same language. That means you need a sound knowledge of that language. That’s the topic of this article. 

Here are the four basic concepts that you should practice to become better at Node.js. I’ll try to keep this article short. 

1. Non-blocking or Asynchronous I/O

Since Node.js is a server-side framework, one of it’s main works is to handle browser requests. In traditional I/O systems, a request can only be issued when the response (the HTML page) of the previous request has arrived. That’s why, it called blocking I/O. The server blocks other requests in order to process the current request which causes the browser to wait (the rotating circle).

Node.js doesn’t follow this principle of I/O. If a request is intended to take longer time, Node.js sends that request in an event loop (I’ll explain this in another article) and goes on to handle the next request in the call stack. As soon as the pending request is done processing, it tells Node.js and and the response is rendered on the browser.

Lets understand this with a dummy example:

Blocking I/O

// take order for table 1 and wait...
var order1 = orderBlocking(['Coke', 'Iced Tea']);

// once order is ready, take order back to table.
// once order is delivered, move on to another table.

// take order for table 2 and wait...
var order2 = orderBlocking(['Coke', 'Water']);


// take order for table 3 and wait...
var order3 = orderBlocking(['Iced Tea', 'Water']);


In this example of a restaurant, the waiter takes an order, waits for the order to be complete, and then goes back to the table to serve that order upon its completion. During the time the order is processing, the waiter just waits or blocks orders from other customers.

Non-blocking I/O

// take order for table 1 and move on...
orderNonBlocking(['Coke', 'Iced Tea'], function(drinks){
  return serveOrder(drinks);

// take order for table 2 and move on...
orderNonBlocking(['Beer', 'Whiskey'], function(drinks){
  return serveOrder(drinks);

// take order for table 3 and move on...
orderNonBlocking(['Hamburger', 'Pizza'], function(food){
  return serveOrder(food);

In this example, the waiter takes an order and informs the cook, then goes back to take another order. After the first order is done processing, he takes that order to the respective table,and goes on again taking orders from other customers. The waiter doesn’t waste time by blocking orders from other customers.

2. Prototype

Prototype is a complex concept of JavaScript. Since you are going to use prototypes a lot in Node.js, every JavaScript developer must know about this concept.

In a language that implements classical inheritance like Java or C++, for the purpose of code reuse, you must first make a class (a blueprint for your objects) and then create objects from that class or extend that class. But, there is no concept of classes in JavaScript. You first create an object in JavaScript and then augment your own object or create new objects from it. This is called prototypal inheritence and is implemented through the prototype.

Every JavaScript object is linked to a prototype object from which it can inherit properties. Prototypes are analogous to classes in other OO lanuages but differ in the fact that they themselves are objects. Every object is linked to Object.prototype which comes predefined with JavaScript.

If you look up a property via obj.propName or obj['propName'] and the object does not have such a property which can be checked via obj.hasOwnProperty('propName'), the JavaScript’s runtime looks up the property in its prototype object. If the prototype object also doesn’t have such a property, its own prototype is checked in turn until a match is found or if it has reached to Object.prototype. If that property doesn’t exist in the prototype chain, then it results in a undefined value.

Let's understand with the following example code:

if (typeof Object.create !== 'function') {
    Object.create = function (o) {
        var F = function () {};
        F.prototype = o;
        return new F();

var otherPerson = Object.create(person);

When you make a new object, you must select an object that should be its prototype. Here, we are adding a create method to the Object  function. The create method creates a new object that uses another object as it’s prototype that was passed to it as an argument.

When we make changes to the new object, its prototype remains unaffected. But, when we make changes to the prototype object, the changes becomes visible in all the objects that are based on that prototype.

Prototype is a complex concept. I’ll be covering on prototype in detail in another post.

3. Modules

If you’ve ever worked with packages in Java, modules in Node.js in no different thing. If not, don’t worry. Modules are simple JavaScript files that contain code for a specific purpose. The module pattern is used to make your code easy to navigate and work with. To use the properties of a module, you have to require it in a JavaScript file much like the same as you import a package in a Java class.

There are two types of modules in Node.js.

Core Modules – These are the ones which come pre-compiled with Node.js library. The purpose of core modules is to provide developers often occurring and repeating code sections that if not available would result in a tedious task for developers because they have to write the same code again and again. Some common core modules are HTTP, URL, EVENTS, FILE SYSTEM, etc.

User Defined Modules – User defined modules are the ones which a developer makes for a specific purpose in its application. These are required when the core modules are not capable of fulfilling the desired functionality.

Modules are extracted via the require function. If its a core module, the argument is simply the name of that module. If it’s a user defined module, then the argument is the path of that module in the file system. For example:

// extract a core module like this

var http = require('http);

// extract a user defined module like this

var something = require('./folder1/folder2/folder3/something.js');

4. Callbacks

In JavaScript, functions are regarded as first-class objects. That means you can do all the operations with functions that you can do with regular objects. You can assign functions to a variable, pass these as arguments to methods, declare them as a property of an object, and even return them from functions.

Callbacks are anonymous functions in JavaScript that can be passed as arguments to other functions and either be executed or returned from that function to be executed later. This is the basis of callbacks, the most widely used functional programming paradigm.

When we pass a callback function as an argument to another function, we only pass the function definition... in other words, we never know when that callback function will execute. That totally depends on the mechanism of the calling function. It is “called back” at some later point of time, hence the name. This is the sole basis of the non-blocking or asynchronous behavior of Node.js as illustrated by the following example.

setTimeout(function() {
}, 2000)


This is one of the simplest examples of a callback. We passed an anonymous function as an argument which simply logs some output on the console to the setTimeout function. Since it’s only the function definition, it doesn’t know when to execute. That is determined by the calling setTimeout function via the second argument, which is after 2 seconds.

First, the second log statement logs the output to the console and then after two seconds, the log statement in the callback function logs the output.

// output


That’s it. Those were my top 4 JavaScript concepts which must be known to a Node.js beginner. What's in your list? Feel free to leave me a comment!

node js ,javascript ,async ,js ,web dev

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}