I am learning through the architecture of Node.js. I have following questions.
- Is event loop a part of libuv or v8?
- Is event queue a part of event loop? are event queue generated by libuv or v8 engine or event loop itself?
- What is the connection between libuv and v8 engine?
- If event loop is single threaded, does libuv come into picture to create multiple threads to handle File I/O?
- Does browsers have event loop mechanism or just Node.js does?
The event loop is, first and foremost, a high-level concept that's a fundamental part of the JavaScript programming model. Practically, every V8 embedder needs to implement an event loop. V8 provides a default implementation, which embedders can replace or extend.
I don't understand the question. (I guess the answer is "yes", but what's the difference between "event loop" and "event queue"?)
None. (Except that Node.js uses both.)
Yes, the event loop is single-threaded.
Yes, browsers have an event loop too (see question 1).
This is actually not as simple as given in the post selected as the answer. I hope my remarks will be a bit more exact. Hopefully I understood Sam Roberts (IBM) correctly in his talk on the Node event loop.
To view the talk yourself you can go here: https://www.youtube.com/watch?v=P9csgxBgaZ8
This is an addon to the answer given by @jmrk
Libuv delegates tasks to the underlying operating system. The operating system then becomes responsible for sending a notification when an event occurs you are listening to. It does this for a lot of the operations you perform in Node. Like: sockets (net/dgram/http/tls/https/child_process pipes, stdin, out, err), timeouts and intervals.
However not everything can be delagated like this to the underlying OS. Sometimes it is required to create a thread (there are 4 treads by default but you can change this using UV_THREADPOOL_SIZE). Not pollable are file system operations, dns.lookup() and some crypto functions.
来源：https://stackoverflow.com/questions/49811043/relationship-between-event-loop-libuv-and-v8-engine