Node.js Event Loop Explained — {link} This article covers the main components of Node.js with practical examples so that people can actually run the snippet and play with it.

I read many articles on how Node.js works internally, but I didn’t find any satisfactory answer, and hence I decided to write an article myself with practical examples so that people can actually run the snippet and play with it.

Primarily I’ll be covering the main components of this architecture like ‘Event Loop,’ ‘Event Queue,’ and a few concepts like ‘blocking’ and ‘non-blocking’ codes.

I’ll take an example of an HTTP API endpoint written in express (the most popular framework of Node.js). Towards the end, I’ll also try to explain why it is said not to use Node.js for CPU-intensive applications (because it is completely related to what we’re going to discuss).

Event Loop: An event loop is an endless loop, which waits for tasks, executes them, and then waits 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.

Event Queue: The event Queue is the list of pending callback functions to be executed. Once an operation is completed, a callback assigned to that operation is added to the event queue, which will eventually be picked by the event loop.

Nodejs single-threaded event loop architecture: As there is only a single thread, only one task can be executed at a time, and a task could be anything; it could be listening for new requests via event loop, or it could be the execution of statements, let’s dive deep into the example.

A function that can keep looping for given milliseconds (can keep the event loop busy).

Script to call these APIs programmatically. Note: These many parameters are returned to support the explanation. Experiment 1:

Why Is Node.js’s Async Nature Not Helping Here?

While API1 was invoked with 5s and API2 was invoked with 2s, so ideally, API2 should respond first. But no, and that’s where the secret is “how Node.js internally works” on a single thread. Let’s understand this in detail.

1. Invocation started for API1 first, so obviously, it reached to event loop first, and the event loop was available and immediately started its execution.
2. As the nature of the API is blocking, it’s a for loop running for given seconds, so the event loop will be busy executing this, and it’ll not be available for taking new requests for a given timeout value (for this example, 5s).
3. After completion of this 5s, the next statement is to return the response; an event loop will follow that, and the response will be returned.
4. Now event loop is available to take new requests, and you can see that the start time of API2 (2022–09–10T05:28:27.854Z) is after the end time of API1 (2022–09–10T05:28:29.859Z).
5. And API2 will start execution, and as this is a waiting call, after a given timeout (2s in this case) callback function will be given to the event queue and event loop (who will be free to take items from the event queue) will dequeue this function and will execute it and will return the response (as written in the code).
6. From the timeline perspective, if API1 and API2 are invoked at the 0th second in this sequence (first API1 and then API2 in parallel), then API1 will respond at the 5th second, and API2 will respond at the 7th second.

Now let’s do another experiment and reverse the order of APIs. Experiment 2:

How Exactly Both the APIs Responded at the Same Time

While section 1 was invoked with 2s, and section 2 was invoked with 5s, so ideally, section 1 should respond first. Let’s understand this in detail.

1. Invocation started for API2 first, so obviously, it reached to event loop first, and the event loop was available and immediately started its execution.
2. As the nature of this API (API2) is non-blocking, so the event loop will start its execution and will be free from this, and it’ll be ready to take the next requests.
3. At this time, API1 will be reached the event loop and start its execution.
4. As the nature of the API (API1) is blocking, it is a for loop running for given seconds, so the event loop will be busy executing this, and it’ll not be available for taking requests for the event queue for a given timeout value (for this example 5s).
5. After completion of this 5s, the next statement is to return the response; an event loop will follow that, and the response will be returned for API1.
6. Now event loop will be free to take requests from the event queue where the timeout function of API2 will be waiting from the last 3s; it will dequeue this function, execute it, and return the response (as written in the code).
7. From the timeline perspective, if API2 and API1 are invoked at the 0th second in this sequence (first API2 and then API1 in parallel), then API1 will respond at the 5th second, and API2 will respond at the 5th second (API2 will respond immediately after API1).

I hope now the internal working of Node.js is clear, and it is also clear why not to use Node.js for CPU-intensive applications.

Read More: WordPress Migration to Google Cloud (Full Guide)

Terraform vs CloudFormation: Comparing The Two Infrastructure As Code Offerings (2022)

https://cronosasia.com/technical/iaas-vs-paas-vs-saas/