Wouldn’t it be awesome if you only had to know 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. Though originally written in C++, it uses JavaScript to be used in applications.
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 must have a sound knowledge of that language.
Here are the four bare minimum concepts that you should be able to put in practice to use Node.js effectively.
1. Non-blocking or Asynchronous I/O
Since Node.js is a server side framework, one of its main operations 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. The server blocks other requests, called blocking I/O, 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, Node sends that request in an event loop (which I’ll explain in greater depth in a different 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 the response is rendered on the browser.
Let’s understand this with a dummy example:
Blocking I/O
In this example of a restaurant, the waiter takes an order, waits for the order to complete, and then goes back to the table to serve the order each time. During the time the order is processing, the waiter just waits or blocks orders from other customers.
Non blocking I/O
In this example, the waiter takes an order, informs the cook of that order, and goes back to take another order. After the first order is done processing, the waiter takes that order to the respective table and goes on again to take orders from other customers. In contrast with the first example, the waiter doesn’t block 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 first make a class (a blueprint for your objects) and then you create objects from that class or extend that class to inherit its properties.
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 inheritance, meaning that objects are implemented through the prototype, not through classes.
Every JavaScript object is linked to a prototype object from which it can inherit properties. Prototypes are analogous to classes in other OO languages but differ in the fact that they are objects themselves. 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’) , then 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 Object.prototype. If that property doesn’t exist in the prototype chain, then it results in an undefined value.
Let’s illustrate that with the following sample code:
When you make a new object, you can 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 its prototype by passing the other object as an argument to the create method. 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 discussing it in detail in another post.
3. Modules
If you’ve ever worked with packages in Java, modules in Node.js is no different. If you haven’t, 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 packages in a Java class. There are two types of modules in Node.js:
- Core Modules – These are the ones that come pre-compiled with the Node.js library. The purpose of core modules is to provide developers with often occurring and repeating code sections that, if they were 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 his/her application. These are required when the core modules are not capable of fulfilling the desired functionality.
Modules are extracted via the require function. If it’s 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,
4. Callbacks
In JavaScript, functions are regarded as first-class objects. That means you can do all the operations with a function 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, the most widely used functional programming paradigm, are anonymous functions in JavaScript that can be passed as arguments to other functions and can be executed or returned from that function to be executed later.
When we pass a callback function as an argument to another function, we only pass the function definition, i.e., we never know when that callback function will execute. The timing of the execution solely depends on the mechanism of the calling function. It is “called back” at some later point of time, hence the name. That’s the sole basis of the non-blocking or asynchronous behavior of Node.js as illustrated by the following example.
This is one of the simplest example 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, the function doesn’t know when to execute. The execution time is determined by the calling setTimeout function via the second argument, which determines that it will be executed 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.
That’s it. These are my top four JavaScript concepts which Node.js beginners would be wise to learn to be better programmers.
What is in your list? Please tell me in the comments.
| Reference: | Top 4 Javascript Concepts a Node.js Beginner Must Know from our WCG partner John Sonmez at the Making the Complex Simple blog. |
It would appear that your code snippets won’t load, so I can’t actually see any of the examples.