How to handle concurrency in Node.js ?
Last Updated : 28 Sep, 2022
Node.js is an open-source, cross-platform runtime environment built on Chrome's V8 Engine. It is used to develop highly scalable backend as well as server-side applications.
Node.js uses a single-threaded event loop architecture. It is also asynchronous in nature. These are the two main reasons why node.js can handle multiple concurrent requests easily and why it becomes an obvious choice for the development of such applications.
Working of Node.js
Working of Node.JS Node.js works asynchronously. In other words, it does not block incoming requests from clients when the operating system has one I/O intensive request. Instead, it passes this I/O request to the internal C++ threads and takes up the next job from the event queue.
Note: The internal C++ threads may or may not be one, but that is not of concern here.
The event queue is nothing but a queue that stores the incoming requests in the order that it received them. It then passes on these requests to the Event Loop when it is available. For every I/O request, the event loop receives, passes it on to the internal C++ threads for processing and makes itself available for the other requests, and starts processing those. Then it uses the concept of callback functions from JavaScript to receive the responses of the tasks that were sent to the internal C++ threads earlier for processing and delivers them to the client.
Let's understand this with an example:
Example 1: Traditional Web Architecture
JavaScript function func() { console.log("Hey I am Line number 1"); setTimeout(function () { console.log("Hey I am Line number 2"); }, 2000); console.log("Hey I am Line number 3"); } console.log("Hey I am Line number 4"); func(); Here, we have 4 console.log() statements in the order of 1 to 4. Assuming this as a traditional architecture-based application, the output would look something like this.
Output:
Hey I am Line number 4 Hey I am Line number 1 Hey I am Line number 3 Hey I am Line number 2
Explanation: Here, the "Hey I am Line number 4" will get executed first as it is above the function call. After that, the function will be called. Then "Hey I am Line number 1" will be printed and the application will add callback passed to setTimeout into browser macrotask queue, print "Hey I am Line number 3" respectively and then when time specified as 2-nd argument of setTimeout exceedes, JS event loop will get callback function from queue and execute it, thus printing "Hey I am Line number 2".
Example 2: Node.js Application
JavaScript function func() { console.log("Hey I am Line number 1"); setTimeout(function () { console.log("Hey I am Line number 2"); }, 2000); console.log("Hey I am Line number 3"); } console.log("Hey I am Line number 4"); func(); Here, we have 4 console.log() statements in the order 1 to 4. Assuming this as a single-threaded non-blocking application, the output would look something like this.
Output:
Hey I am Line number 4 Hey I am Line number 1 Hey I am Line number 3 Hey I am Line number 2
Explanation: Here, the "Hey I am Line number 4" will get executed first as it is above the function call. After that, the function will be called. Then "Hey I am Line number 1" will be printed and the application will go into a timeout due to the function call, for 2 seconds (2000 ms). Now, when the application is waiting for 2 seconds, it will not block further requests, it will instead process the next request and thus print "Hey I am Line number 3". Once the timeout is finished, the lines will now be executed and "Hey I am Line number 2" will be printed to the console.
In this way, the event loop never stays occupied or blocked by a particular request. This is what gives Node.js a competitive advantage over traditional web servers in terms of handling multiple user requests at the same time, i.e. concurrency.
Similar Reads
How to Handle Errors in Node.js ?
Node.js is a JavaScript extension used for server-side scripting. Error handling is a mandatory step in application development. A Node.js developer may work with both synchronous and asynchronous functions simultaneously. Handling errors in asynchronous functions is important because their behavior
4 min read
How to Copy a File in Node.js?
Node.js, with its robust file system (fs) module, offers several methods to copy files. Whether you're building a command-line tool, a web server, or a desktop application, understanding how to copy files is essential. This article will explore various ways to copy a file in Node.js, catering to bot
2 min read
If Node.js is single threaded then how to handles concurrency ?
Node js is an open-source virtual machine that uses javascript as its scripting language. Despite being single-threaded, it is one of the most popular web technologies. The reason why node js is popular despite being single-threaded is the asynchronous nature that makes it possible to handle concurr
4 min read
How to Handle Errors for Async Code in Node.js ?
Handling errors effectively in asynchronous code is crucial for building robust and reliable Node.js applications. As Node.js operates asynchronously by default, understanding how to manage errors in such an environment can save you from unexpected crashes and ensure a smooth user experience. This a
4 min read
How to handle Child Threads in Node.js ?
Node.js is a single-threaded language and uses the multiple threads in the background for certain tasks as I/O calls but it does not expose child threads to the developer.But node.js gives us ways to work around if we really need to do some work parallelly to our main single thread process.Child Pro
2 min read
How to Handle CPU Intensive Loads In Node JS ?
Node is a Single-Threaded Non-blocking event-driven architecture. But when it comes to handling heavy CPU-intensive workloads it can face some challenges while handling it. In this article, we will explore strategies to tackle CPU-intensive loads in Node.js effectively, to handle demanding tasks lik
5 min read
How to Access Cache Data in Node.js ?
Caching is an essential technique in software development that helps improve application performance and scalability by temporarily storing frequently accessed data. In Node.js, caching can significantly reduce database load, minimize API response times, and optimize resource utilization. This artic
5 min read
How to Avoid Callback Hell in Node.js ?
Callback hell, often referred to as "Pyramid of Doom," occurs in Node.js when multiple nested callbacks lead to code that is hard to read, maintain, and debug. This situation arises when each asynchronous operation depends on the completion of the previous one, resulting in deeply nested callback fu
3 min read
How to handle asynchronous operations in Node ?
NodeJS, renowned for its asynchronous and event-driven architecture, offers powerful mechanisms for handling asynchronous operations efficiently. Understanding how to manage asynchronous operations is crucial for NodeJS developers to build responsive and scalable applications. What are Asynchronous
2 min read
How To Handle Global Connection of MongoDB in NodeJs?
Handling a global connection to MongoDB in a Node.js application is important for efficient resource management and performance optimization. By maintaining a single connection to the MongoDB database, you avoid the overhead of repeatedly establishing and closing connections, which can be resource-i
2 min read