My favorite thing in software engineering is the art of making it transparent. 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. I spent months working on a course to demystify NodeJS Internals and Architecture and distilled this in this comprehensive course. I built this course is for the engineers who can’t stand working with something opaque.
- They love to understand what is running behind the engine.
- They enjoy tearing apart 1 the line of code into its original 1000 lines.
- They question why is the output of a Node program is unpredictable.
- They want to know when does the Node process exit.
- They want to know why Node takes so long to start in some cases.
- They appreciate how Node works on all operating systems and would like to know how it does that.
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. 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.
