11-21-2018, 12:48 AM
Learn Node.js, Unit 3: A tour of Node.js
<div style="margin: 5px 5% 10px 5%;"><img src="http://www.sickgaming.net/blog/wp-content/uploads/2018/11/learn-node-js-unit-3-a-tour-of-node-js.png" width="1082" height="848" title="" alt="" /></div><div><div class="lcom-stacked__main">
<div class="panel-pane pane-entity-field pane-node-body">
<div class="field field-name-body field-type-text-with-summary field-label-hidden">
<div class="field-items">
<div class="field-item even">
<p>Node is often described as “JavaScript on the server”, but that doesn’t quite do it justice. In fact, any description of Node.js I can offer will be unfairly reductionist, so let me start with the one provided by the Node team:</p>
<p>“Node.js is a JavaScript runtime built on Chrome’s V8 JavaScript engine.” (<a href="https://nodejs.org/en/">Source</a>)</p>
<p>That’s a fine description, but it kinda needs a picture, doesn’t it? If you look on the Node.js website, you’ll notice there are no high-level diagrams of the Node.js architecture. Yet, if you search for “Node.js architecture diagram” there are approximately 178 billion different diagrams that attempt to paint an overall picture of Node (I’ll refer to Node.js as Node from now on). After looking at a few of them, I just didn’t see one that fit with the way I’ve structured the material in this course, so I came up with this:</p>
<p><img alt="Node Architecture" src="http://www.sickgaming.net/blog/wp-content/uploads/2018/11/learn-node-js-unit-3-a-tour-of-node-js.png" /></p>
<p>Figure 1. The Node.js architecture stack</p>
<p>Read more at<a href="http://https//developer.ibm.com/tutorials/learn-nodejs-tour-node/"> IBM Developers</a></p>
</div>
</div>
</div></div>
</p></div>
<p><a href="https://www.linux.com/popup/nojs" class="ctools-use-modal ctools-modal-subscription-modal-style element-invisible" title="">Click Here!</a> </p>
</div>
<div style="margin: 5px 5% 10px 5%;"><img src="http://www.sickgaming.net/blog/wp-content/uploads/2018/11/learn-node-js-unit-3-a-tour-of-node-js.png" width="1082" height="848" title="" alt="" /></div><div><div class="lcom-stacked__main">
<div class="panel-pane pane-entity-field pane-node-body">
<div class="field field-name-body field-type-text-with-summary field-label-hidden">
<div class="field-items">
<div class="field-item even">
<p>Node is often described as “JavaScript on the server”, but that doesn’t quite do it justice. In fact, any description of Node.js I can offer will be unfairly reductionist, so let me start with the one provided by the Node team:</p>
<p>“Node.js is a JavaScript runtime built on Chrome’s V8 JavaScript engine.” (<a href="https://nodejs.org/en/">Source</a>)</p>
<p>That’s a fine description, but it kinda needs a picture, doesn’t it? If you look on the Node.js website, you’ll notice there are no high-level diagrams of the Node.js architecture. Yet, if you search for “Node.js architecture diagram” there are approximately 178 billion different diagrams that attempt to paint an overall picture of Node (I’ll refer to Node.js as Node from now on). After looking at a few of them, I just didn’t see one that fit with the way I’ve structured the material in this course, so I came up with this:</p>
<p><img alt="Node Architecture" src="http://www.sickgaming.net/blog/wp-content/uploads/2018/11/learn-node-js-unit-3-a-tour-of-node-js.png" /></p>
<p>Figure 1. The Node.js architecture stack</p>
<p>Read more at<a href="http://https//developer.ibm.com/tutorials/learn-nodejs-tour-node/"> IBM Developers</a></p>
</div>
</div>
</div></div>
</p></div>
<p><a href="https://www.linux.com/popup/nojs" class="ctools-use-modal ctools-modal-subscription-modal-style element-invisible" title="">Click Here!</a> </p>
</div>