From eb9cdce34cef2172dc05fb91d0d0b7e2d316cc7c Mon Sep 17 00:00:00 2001 From: zeus Date: Fri, 26 Nov 2021 16:30:40 +0200 Subject: [PATCH] edit poc --- poc-datacollector/modules/ROOT/pages/index-nodejs.adoc | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/poc-datacollector/modules/ROOT/pages/index-nodejs.adoc b/poc-datacollector/modules/ROOT/pages/index-nodejs.adoc index 6609d65..08b38cf 100644 --- a/poc-datacollector/modules/ROOT/pages/index-nodejs.adoc +++ b/poc-datacollector/modules/ROOT/pages/index-nodejs.adoc @@ -1,6 +1,6 @@ = NodeJS -> services readmongo_service, dummy_service - +== asynchronous event-driven TIP: As an asynchronous event-driven JavaScript runtime, Node.js is designed to build scalable network applications. @@ -29,6 +29,7 @@ In Node.js, there is no such start-the-event-loop call. - *Node.js exits the event loop* when there are *no more callbacks to perform.* ==== +== threads Node.js being *designed without threads* doesn't mean you can't take advantage of multiple cores in your environment. @@ -37,7 +38,7 @@ Child processes can be spawned by using our *child_process.fork() API,* and are TIP: Built upon that same interface is the cluster module, which *allows you to share sockets between processes* to enable load balancing over your cores. -=== Video = intro +== Video = intro ****