thomasabishop/eolas
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Last Sync: 2022-07-15 08:00:04

Browse source
This commit is contained in:
tactonbishop 2022-07-15 08:00:04 +01:00
parent 86abdc1811
commit 3e7d2a0722
2 changed files with 0 additions and 13 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

0
Programming_Languages/NodeJS/Architecture/Events.md → Programming_Languages/NodeJS/Architecture/Event_loop.md
View file

13
Programming_Languages/NodeJS/Architecture/Event_queue.md
View file

@ -1,13 +0,0 @@
---
tags:
- Programming_Languages
- backend
- node-js
- async
---
We know that Node works by managing [request-response transactions asynchronously](Single-threaded%20asynchronous%20architecture.md) but how does it achieve this? It does it via the Event Queue. This is the mechanism by which Node keeps track of incoming requests and their fulfillment status: whether the data has been returned successfully or if there has been error.
Node is continually monitoring the Event Queue in the background.
This makes Node ideal for applications that require a lot of disk or network I/O access. However it means it is not well-positioned to build applications that are CPU intensive such as image rendering and manipulation.