From 3e7d2a0722049c1472a70d7b05dac6da2b1ccb53 Mon Sep 17 00:00:00 2001 From: tactonbishop Date: Fri, 15 Jul 2022 08:00:04 +0100 Subject: [PATCH] Last Sync: 2022-07-15 08:00:04 --- .../Architecture/{Events.md => Event_loop.md} | 0 .../NodeJS/Architecture/Event_queue.md | 13 ------------- 2 files changed, 13 deletions(-) rename Programming_Languages/NodeJS/Architecture/{Events.md => Event_loop.md} (100%) delete mode 100644 Programming_Languages/NodeJS/Architecture/Event_queue.md diff --git a/Programming_Languages/NodeJS/Architecture/Events.md b/Programming_Languages/NodeJS/Architecture/Event_loop.md similarity index 100% rename from Programming_Languages/NodeJS/Architecture/Events.md rename to Programming_Languages/NodeJS/Architecture/Event_loop.md diff --git a/Programming_Languages/NodeJS/Architecture/Event_queue.md b/Programming_Languages/NodeJS/Architecture/Event_queue.md deleted file mode 100644 index 26a3711..0000000 --- a/Programming_Languages/NodeJS/Architecture/Event_queue.md +++ /dev/null @@ -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.