NodeJS Internals and Architecture

<div>My favorite thing in software engineering is the art of making it transparent.</div><div><br></div><div><span style="font-size: 1rem;">Node is one of the most popular runtimes used on backend engineering yet I feel it is the least understood. I surely felt this way at times.</span></div><div><br></div><div><span style="font-size: 1rem;">I spent months working on a course to demystify NodeJS Internals and Architecture and distilled this in this comprehensive course.</span></div><div><br></div><div><span style="font-size: 1rem;">I built this course is for the engineers who can't stand working with something opaque.</span></div><div><br></div><div><span style="font-size: 1rem;">They love to understand what is running behind the engine.</span></div><div><br></div><div>They enjoy tearing apart 1 the line of code into its original 1000 lines.</div><div><br></div><div>They question why is the output of a Node program is unpredictable.</div><div><br></div><div>They want to know when does the Node process exit.</div><div><br></div><div>They want to know why Node takes so long to start in some cases.</div><div><br></div><div>They appreciate how Node works on all operating systems and would like to know how it does that.</div><div><br></div><div><span style="font-size: 1rem;">For example by understanding the internals of HTTP module, you can write a backend in Node that accepts and process more requests. Every line of code you write you would think of how and when Node will process it.</span></div><div><br></div><div><span style="font-size: 1rem;">By understanding the event loop and the different stages you can tune and re-order your code to achieve best performance and even consistent result.</span></div><div><br></div><div><span style="font-size: 1rem;">Ever wrote a program in Node that fails 1% of the time while succeeds 99%? Understanding Node architecture helps you make your program predicable. As opposed to adding workaround because you don't understand. We all did that.</span></div><div><br></div><div><span style="font-size: 1rem;">It is all about removing blockage and letting the main loop phases “breath”. When we build software the problem is we often go against the grain. Understanding where the friction is in Node allow you to work with it as oppose to against it.</span></div><div><br></div><div><span style="font-size: 1rem;">In this course I cover the following</span></div><div><br></div><div>- NodeJS Architecture</div><div><br></div><div>I cover the various phases in the event loop and what exactly happens in each phase, how promises are just callbacks, how and when modules are loaded and their effect on performance, Node packages anatomy and more</div><div><br></div><div>- Node Internals</div><div><br></div><div>This is where we go one layer deeper, how Node truly achieves asynchronous IO with libuv, and how each protocol in node is implemented. How concurrent node works on both user level threads and process level.</div><div><br></div><div><span style="font-size: 1rem;">- Node Optimization and Performance</span></div><div><br></div><div>Now that we understand the internals and architecture of Node, this is where we discuss tips how to make the code runs more efficiently and more performance. And only when we exhaust all other avenues Node provides ways to extend it with C++ add-ons where JavaScript just can't no longer hold.</div><div><br></div><div><span style="font-size: 1rem;">This course is for intermediate students who are familiar with Node and want to understand how it works. While not required, I recommend taking the fundamentals of operating system course as a prerequisite of this course.</span></div>

What you'll learn:

• NodeJS Architecture
• NodeJS protocols, file and socket programming internals
• Optimize Node JS
• Writing efficient code
• Multi-threaded Node
• Libuv Asynchronous IO
• Node Networking
• Node Streams
• C++ Addons