Skip to main content

Node Architecture

Node.js is based upon an event-driven, light-weight, and non-blocking I/O model. This is a lightweight, minimal framework based on the Google Chrome V8 engine. The Event-loops are the soul of event-driven programming, almost all the programs using UI use event-loops to detect and react to the user events.
Like Clicking a button, Ajax Requests, etc.

Node.js is a command-line tool(See getting started with Node). It is a high-performance network application, JavaScript minimal framework well suitable for the concurrent environments. Node is not just JavaScript, its major part is written in C/C++.

Node.js Architecture


Node uses event-loops by JavaScript callbacks to implement the non-blocking I/O. (We must always keep in mind that JavaScript used in Node is not exactly same as we know, it is different, in fact, it is no DOM implementation used by Node, so be careful).

Everything inside the Node runs upon a single thread(main thread), and this thread should never be blocked. It means if we need to wait for something to happen, it must provide a callback. So CPU-intensive operation must be kept off from the event-loops.


Event-loops
Event-loops 

Conventional IO Model



var myresults=db.query("Execute some query in database");   
      executeWithResults(myresults);
      //wait forre results to load             
      executeWithOutResult();
      //execution will be blocked untill the
      //executeWith(myresults) finishies              


Non-blocking IO Model



db.query("Execute some query in database",function(myresults){           
      executeWithResults(myresults);//wait for result     
      });  
 executeWithOutResults(); //executes without any delay!                  


Blocking Vs Non-blocking IO


The conventional model is an asynchronous model. It waits for input before proceeding. The thread is blocked.

Non-blocking IO is asynchronous, the main thread is not blocked and keeps executing without blocking. The Node.js implements a non-blocking IO with event-based JavaScript callbacks.

The biggest advantage of non-blocking IO is no-overhead is associated with the threads, so we can handle lots of client requests at the same time. This is best for achieving the high-concurrency.




Threads consume resources like memory on stack and some processing time is consumed in order to provide context switching among the threads. 

On the other hand, no thread management is required in non-blocking IO. Only JavaScript callbacks are executed when some event occurs. 

These callbacks are usually in the form of anonamous functions.

Comments

Popular posts from this blog

4 Ways to Communicate Across Browser Tabs in Realtime

1. Local Storage Events You might have already used LocalStorage, which is accessible across Tabs within the same application origin. But do you know that it also supports events? You can use this feature to communicate across Browser Tabs, where other Tabs will receive the event once the storage is updated. For example, let’s say in one Tab, we execute the following JavaScript code. window.localStorage.setItem("loggedIn", "true"); The other Tabs which listen to the event will receive it, as shown below. window.addEventListener('storage', (event) => { if (event.storageArea != localStorage) return; if (event.key === 'loggedIn') { // Do something with event.newValue } }); 2. Broadcast Channel API The Broadcast Channel API allows communication between Tabs, Windows, Frames, Iframes, and  Web Workers . One Tab can create and post to a channel as follows. const channel = new BroadcastChannel('app-data'); channel.postMessage(data); And oth...

Certbot SSL configuration in ubuntu

  Introduction Let’s Encrypt is a Certificate Authority (CA) that provides an easy way to obtain and install free  TLS/SSL certificates , thereby enabling encrypted HTTPS on web servers. It simplifies the process by providing a software client, Certbot, that attempts to automate most (if not all) of the required steps. Currently, the entire process of obtaining and installing a certificate is fully automated on both Apache and Nginx. In this tutorial, you will use Certbot to obtain a free SSL certificate for Apache on Ubuntu 18.04 and set up your certificate to renew automatically. This tutorial will use a separate Apache virtual host file instead of the default configuration file.  We recommend  creating new Apache virtual host files for each domain because it helps to avoid common mistakes and maintains the default files as a fallback configuration. Prerequisites To follow this tutorial, you will need: One Ubuntu 18.04 server set up by following this  initial ...

Working with Node.js streams

  Introduction Streams are one of the major features that most Node.js applications rely on, especially when handling HTTP requests, reading/writing files, and making socket communications. Streams are very predictable since we can always expect data, error, and end events when using streams. This article will teach Node developers how to use streams to efficiently handle large amounts of data. This is a typical real-world challenge faced by Node developers when they have to deal with a large data source, and it may not be feasible to process this data all at once. This article will cover the following topics: Types of streams When to adopt Node.js streams Batching Composing streams in Node.js Transforming data with transform streams Piping streams Error handling Node.js streams Types of streams The following are four main types of streams in Node.js: Readable streams: The readable stream is responsible for reading data from a source file Writable streams: The writable stream is re...