Behind Node.js - The Event Loop

Behind Node.js - The Event Loop

Wojciech Parys - October 15, 2019

Node.js is a JavaScript runtime built on Chrome’s V8 JavaScript Engine. That you can read at the home page of But what Node.js exactly is? How does it work? In this article we will dive into core features of this runtime environment. So let’s move on.

What does mean Javascript Runtime

You probably know what JavaScript is. It’s a programming language, typically used in a browser to manipulate DOM, or to implement some behaviour, like for example opening popups and modals, or interaction with user after the page was loaded.

However, JavaScript is not limited to that. Node.js, which is said to be a “different version of JavaScript”, is basically build on JavaScript, with some features added, and with some features removed, compared to JS running in a browser. It was modified to allow you to use JavaScript on the server side, like any normal programming language used in your computer programs.

NodeJS Architecture A

Node.js uses V8 engine - a JavaScript engine written in C++, that was built by Google and runs JS in the browser. That means that engine takes JavaScript code - the code running in your browser or the Node.js code - and compiles it to the machine code. Node.js takes codebase and adds some features, like working with your local file system, that browser can’t do for security reasons. Of course, some features are missing, like DOM manipulations, cause you don’t have any DOM at the server side ;-)

NodeJS Architecture B

Single- or Multi-Threaded

One important thing is that Node.js uses only one single JavaScript thread (process). So how is it able to handle multiple requests or operations? Let’s say your program accesses the file system. Operations on file system are really fast, but when you have very big files this can be time consuming. So if you’re doing this for an incoming request, a second request might be blocked because you’re not able to handle it yet, or it might even get declined, so your page is basically down for this request. Here the event loop comes in handy.

The event loop is automatically started by Node.js when the program starts. This loop is responsible for handling event callbacks, so it runs some code when a certain event occurs. It doesn’t handle your file operations, it only fires callbacks that you defined when for example the file write is done. That code will be handled in the event loop but it will finish very fast.

What about file system operations? They are send to Worker Pool which is also managed by Node.js automatically. This worker pool is responsible for all the heavy lifting and it runs on multiple threads. It’s closely integrated with the operating system you’re running the app on, so it is really detached from your code. So this is where the magic happens. Once the worker is done, it will trigger the callback, and since the event loop is responsible for all events and callbacks, it will end up in the event loop.

Event Loop Multithreading

So let’s take a closer look at the event loop…

Event Loop explained

Event loop is just an infinite loop which is started by Node.js that keeps the Node.js process running. As I mentioned, it handles all the callbacks and it has a certain order in which it goes though the callbacks. The following diagram shows an overview of the event loop’s order of operations:

Event Loop Explained


This phase executes callbacks scheduled by setTimeout() and setInterval(). A timer specifies the threshold after which a provided callback may be executed rather than the exact time a user wants it to be executed. Timers’ callbacks will run as early as they can be scheduled after a specified amount of time has passed. However, Operating System schedulers or the running of other callbacks may delay them.

Pending callbacks

In this phase I/O-related callbacks will be executed, deferred to the next loop iteration. For example, if you registered a callback fired after write or read to file has finished, or some network operation is completed, this callback will run in this phase.

Idle, prepare

They’re only used internally.


It’s basically a phase where nodejs looks for a new IO events and do it’s best to execute their callbacks immediately if possible. If not, it will defer a callback execution and register this as a pending callback. So it has two main responsibilities:

  1. Calculate how long it should block until next I/O polling
  2. Process events in the polling queue.

It also checks if there are any timer callbacks and if so, it jumps to that timer phase and execute them right away. This means that it can jump back not completing the iteration. If there are no timers awaiting it will continue.


setImmediate() callbacks are invoked here. This is something like setTimeout or setInterval, but it will execute immediately, after any open callbacks have been executed.

Close callbacks

Here node execute all “close” event callbacks. So if you registered any close event in your code, eg: socket.destroy() this is, where it will be executed.


So this is basically how Node.js event loop works. If you would like to delve even deeper into the topic, there is a lot of interesting stuff in the Node.js documentation, where you can read more and for example find differences between setImmediate and setTimeout functions, and understand the process.nextTrick() method. Also you can read more about application architecture here!

About the author

Wojciech Parys

Wojciech Parys

Software Engineer

Linkedin profile Github profile

Wojciech is a Javascript developer with many years of experience. He's always striving to find new ways to evolve and expand his knowledge to be the best he can for himself and others. One thing that sets him apart from other frontend developers is his understanding of backend nature, which he gained through working on many projects as an experienced professional. Wojciech has experience in various frameworks and technologies, giving him a uniquely diverse skill set. Wojciech brings a whole new dimension to his work by being able to contribute significant project improvements.

Tempted to work
on something
as creative?

That’s all we do.

join nexocode

This article is a part of

Zero Legacy
36 articles

Zero Legacy

What goes on behind the scenes in our engineering team? How do we solve large-scale technical challenges? How do we ensure our applications run smoothly? How do we perform testing and strive for clean code?

Follow our article series to get insight into our developers' current work and learn from their experience. Expect to see technical details, architecture discussions, reviews on libraries and tools we use, best practices on software quality, and maybe even some fail stories.

check it out

Zero Legacy

Insights from nexocode team just one click away

Sign up for our newsletter and don't miss out on the updates from our team on engineering and teal culture.


Thanks for joining the newsletter

Check your inbox for the confirmation email & enjoy the read!

This site uses cookies for analytical purposes.

Accept Privacy Policy

In the interests of your safety and to implement the principle of lawful, reliable and transparent processing of your personal data when using our services, we developed this document called the Privacy Policy. This document regulates the processing and protection of Users’ personal data in connection with their use of the Website and has been prepared by Nexocode.

To ensure the protection of Users' personal data, Nexocode applies appropriate organizational and technical solutions to prevent privacy breaches. Nexocode implements measures to ensure security at the level which ensures compliance with applicable Polish and European laws such as:

  1. Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation) (published in the Official Journal of the European Union L 119, p 1); Act of 10 May 2018 on personal data protection (published in the Journal of Laws of 2018, item 1000);
  2. Act of 18 July 2002 on providing services by electronic means;
  3. Telecommunications Law of 16 July 2004.

The Website is secured by the SSL protocol, which provides secure data transmission on the Internet.

1. Definitions

  1. User – a person that uses the Website, i.e. a natural person with full legal capacity, a legal person, or an organizational unit which is not a legal person to which specific provisions grant legal capacity.
  2. Nexocode – NEXOCODE sp. z o.o. with its registered office in Kraków, ul. Wadowicka 7, 30-347 Kraków, entered into the Register of Entrepreneurs of the National Court Register kept by the District Court for Kraków-Śródmieście in Kraków, 11th Commercial Department of the National Court Register, under the KRS number: 0000686992, NIP: 6762533324.
  3. Website – website run by Nexocode, at the URL: whose content is available to authorized persons.
  4. Cookies – small files saved by the server on the User's computer, which the server can read when when the website is accessed from the computer.
  5. SSL protocol – a special standard for transmitting data on the Internet which unlike ordinary methods of data transmission encrypts data transmission.
  6. System log – the information that the User's computer transmits to the server which may contain various data (e.g. the user’s IP number), allowing to determine the approximate location where the connection came from.
  7. IP address – individual number which is usually assigned to every computer connected to the Internet. The IP number can be permanently associated with the computer (static) or assigned to a given connection (dynamic).
  8. GDPR – Regulation 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of individuals regarding the processing of personal data and onthe free transmission of such data, repealing Directive 95/46 / EC (General Data Protection Regulation).
  9. Personal data – information about an identified or identifiable natural person ("data subject"). An identifiable natural person is a person who can be directly or indirectly identified, in particular on the basis of identifiers such as name, identification number, location data, online identifiers or one or more specific factors determining the physical, physiological, genetic, mental, economic, cultural or social identity of a natural person.
  10. Processing – any operations performed on personal data, such as collecting, recording, storing, developing, modifying, sharing, and deleting, especially when performed in IT systems.

2. Cookies

The Website is secured by the SSL protocol, which provides secure data transmission on the Internet. The Website, in accordance with art. 173 of the Telecommunications Act of 16 July 2004 of the Republic of Poland, uses Cookies, i.e. data, in particular text files, stored on the User's end device.
Cookies are used to:

  1. improve user experience and facilitate navigation on the site;
  2. help to identify returning Users who access the website using the device on which Cookies were saved;
  3. creating statistics which help to understand how the Users use websites, which allows to improve their structure and content;
  4. adjusting the content of the Website pages to specific User’s preferences and optimizing the websites website experience to the each User's individual needs.

Cookies usually contain the name of the website from which they originate, their storage time on the end device and a unique number. On our Website, we use the following types of Cookies:

  • "Session" – cookie files stored on the User's end device until the Uses logs out, leaves the website or turns off the web browser;
  • "Persistent" – cookie files stored on the User's end device for the time specified in the Cookie file parameters or until they are deleted by the User;
  • "Performance" – cookies used specifically for gathering data on how visitors use a website to measure the performance of a website;
  • "Strictly necessary" – essential for browsing the website and using its features, such as accessing secure areas of the site;
  • "Functional" – cookies enabling remembering the settings selected by the User and personalizing the User interface;
  • "First-party" – cookies stored by the Website;
  • "Third-party" – cookies derived from a website other than the Website;
  • "Facebook cookies" – You should read Facebook cookies policy:
  • "Other Google cookies" – Refer to Google cookie policy:

3. How System Logs work on the Website

User's activity on the Website, including the User’s Personal Data, is recorded in System Logs. The information collected in the Logs is processed primarily for purposes related to the provision of services, i.e. for the purposes of:

  • analytics – to improve the quality of services provided by us as part of the Website and adapt its functionalities to the needs of the Users. The legal basis for processing in this case is the legitimate interest of Nexocode consisting in analyzing Users' activities and their preferences;
  • fraud detection, identification and countering threats to stability and correct operation of the Website.

4. Cookie mechanism on the Website

Our site uses basic cookies that facilitate the use of its resources. Cookies contain useful information and are stored on the User's computer – our server can read them when connecting to this computer again. Most web browsers allow cookies to be stored on the User's end device by default. Each User can change their Cookie settings in the web browser settings menu: Google ChromeOpen the menu (click the three-dot icon in the upper right corner), Settings > Advanced. In the "Privacy and security" section, click the Content Settings button. In the "Cookies and site date" section you can change the following Cookie settings:

  • Deleting cookies,
  • Blocking cookies by default,
  • Default permission for cookies,
  • Saving Cookies and website data by default and clearing them when the browser is closed,
  • Specifying exceptions for Cookies for specific websites or domains

Internet Explorer 6.0 and 7.0
From the browser menu (upper right corner): Tools > Internet Options > Privacy, click the Sites button. Use the slider to set the desired level, confirm the change with the OK button.

Mozilla Firefox
browser menu: Tools > Options > Privacy and security. Activate the “Custom” field. From there, you can check a relevant field to decide whether or not to accept cookies.

Open the browser’s settings menu: Go to the Advanced section > Site Settings > Cookies and site data. From there, adjust the setting: Allow sites to save and read cookie data

In the Safari drop-down menu, select Preferences and click the Security icon.From there, select the desired security level in the "Accept cookies" area.

Disabling Cookies in your browser does not deprive you of access to the resources of the Website. Web browsers, by default, allow storing Cookies on the User's end device. Website Users can freely adjust cookie settings. The web browser allows you to delete cookies. It is also possible to automatically block cookies. Detailed information on this subject is provided in the help or documentation of the specific web browser used by the User. The User can decide not to receive Cookies by changing browser settings. However, disabling Cookies necessary for authentication, security or remembering User preferences may impact user experience, or even make the Website unusable.

5. Additional information

External links may be placed on the Website enabling Users to directly reach other website. Also, while using the Website, cookies may also be placed on the User’s device from other entities, in particular from third parties such as Google, in order to enable the use the functionalities of the Website integrated with these third parties. Each of such providers sets out the rules for the use of cookies in their privacy policy, so for security reasons we recommend that you read the privacy policy document before using these pages. We reserve the right to change this privacy policy at any time by publishing an updated version on our Website. After making the change, the privacy policy will be published on the page with a new date. For more information on the conditions of providing services, in particular the rules of using the Website, contracting, as well as the conditions of accessing content and using the Website, please refer to the the Website’s Terms and Conditions.

Nexocode Team


Want to be a part of our engineering team?

Join our teal organization and work on challenging projects.