Tamar Twena-Stern

A deep dive into the event loop, how it works, what its different phases are, and how it enables non-blocking IO.

Node.js is a very popular server-side framework that is slowly becoming the main platform for developing server-side applications. A lot of phrases are mentioned when developers talk about Node.js, such as ‘Single process with event loop’, ‘Non blocking IO’ , ‘generational garbage collector’, and more. But what do those phrases mean? Is Node.js really single threaded? How do the event loop and other internal mechanisms of the platform really work?

In this talk, I will give an overview on some of the platform internals. We will do a deep dive into the event loop, how it works, what its different phases are, and how it enables non-blocking IO. And, of course, we will answer the repeating question – is the event loop single threaded? We will also talk about the JIT compiler and the v8 engine. The session will end with a look at the garbage collector mechanism, the different algorithms that exists in each garbage collector phase, and how we can monitor our software to start detecting memory leaks.

2019

International JavaScript Conference

A Journey into Node.js Internals

Get familiar with event sourcing on the server and learn how it can be combined into your architecture.

The overall amount of data that our servers have to handle continue to grow every year, as servers need to handle more and more traffic. As such, event sourcing patterns become more useful to handle the load. In this talk, I would like to talk about the different architecture patterns to implement event sourcing in your Node.js server and what architecture can fit every case.