DEV Community

Difference between the Event Loop in Browser and Node Js?

Jasmin Virdi on March 28, 2022

Every JS developer must have heard of the term Event Loop. Both JS and Node Js is based on the principle of event loop which has similarities and d...

Read full post

Dhanush N • Mar 29 '22

Well explained 🙂

Adding on

In a browser when you open a page in a tab, you actually create a process in which there can be multiple threads, such as js engine, page rendering, HTTP request threads and many more. Whereas in nodejs you initiate a request, you actually create a thread that may be destroyed when the request is completed.

Jasmin Virdi • Mar 29 '22

Thanks for adding up☺️

Do you mind if I add this to the difference list in the post?

Dhanush N • Mar 29 '22

Yeah, you can add 🙂

Comment marked as low quality/non-constructive by the community. View Code of Conduct

theoldman • Oct 7 '22 • Edited

what can you even say to a person, who is writing article about event loop and at the same time agreeing with some stupid person who thinks node js creates a thread for every request. WOW, I have no words, the first line of the documentation of the Node JS says node js is single threaded..

Jasmin Virdi • Oct 9 '22 • Edited

Hey,

Thanks for pointing that out. It was incomplete as information and must have created confusion among the readers regarding the concept. I have updated the context. 🙌🏼 🙂

Friendly advice: While pointing out issues in someone's article we can try using polite language instead of calling someone stupid or making fun of them. It is really discouraging for people out there writing articles and others who are sharing their feedback.

This is platform where everyone is sharing their learnings and mistakes are bound to happen for which I apologise. We as developers should help each other by providing valuable feedback in a better way and make this community a better place. 🙂

Khaledinges • Mar 31 '22

"Whereas in Node JS you initiate a request, you actually create a thread that may be destroyed when the request is completed"

It is incomplete as information. This is actually correct for the first request on the server, when you will have other requests or simultaneous requests, Node.js will still have one thread async processing.

Other languages like rust, java, .net have those type of concepts, I mean multi-threading approach.

Rahul Ramteke • Mar 30 '22

Node doesn't always use a thread pool. At its core it relies on operating system's ability to intimate it about certain events, for example kequeue, epoll etc.

The burden of actually executing the async operation and notifying node lies with OS. But for cases where that's not possible, it falls back to the threadpool. For example dns resolution is handled by thread pool, but file and socket operations are mostly OS.

LG • Mar 30 '22 • Edited

Instead of forking (crude-cloning) processes into splitted (distinct) context for each child process,
we instead employ workers (CPU heavy computations e.g. for DNS lookup) within single-threaded-context (thread pool) . I see workers (a.k.a. threads) as some sort of virtualization (optimization) within same boundaries of memory (RAM) at time . This image helped me a lot to comprehend what I stated in my comment above ; I'll be honest I may be mistaken , always welcome to give alternative argument for that .

Rahul Ramteke • Mar 30 '22

That's a nice article! Although, just to re-iterate, I was talking about the threadpool which libuv maintains.
A very brief explaination :
As I mentioned, at its core, node expects the OS to do the heavylifting. And different Operating Systems have different mechanism of doing that, hence node folks built an abstraction library called libuv. This library abstracts event loop and the OS interactions(fun fact, you can use this lib stand alone).
Now, let's say there's an operation which node wants to do differently, or there's something which OS can't handle or doesn't support. To manage such scenarios libuv has its own threadpool, and this threadpool(default size 4) simulates the async behavior which node expects from OS.