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?
A closer look at the Node.js platform
In this talk, Node.js expert Tamar Twena-Stern gives an overview on some of the platform internals. She does 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, she answers the repeating question – is the event loop single threaded? She also talks about the JIT compiler and the v8 engine. The session ends with a look at the garbage collector mechanism, the different algorithms that exists in each garbage collector phase, and how to monitor software to start detecting memory leaks.
Tamar Twena-Stern is a software manager and architect. In the past, she managed a development group in Edgeverve Systems and was an architect of a transaction engine. She also led a team of performance experts at NCR Retail, was a solution architect in Personetics, and had a start up of her own in the social network field.
She has a decade of software engineering experience in various technologies: Server side, big data, mobile, web technologies, and security.
She is currently focusing on Node.js, and has a deep knowledge of Node.js server architecture and Node.js performance optimizations.