NodeSource at Node Interactive 2017

In just over a week, we’ll be heading out to Node.js Interactive 2017! Node.js Interactive is the official Node.js event held by the Node.js Foundation and the de facto venue for the community to connect with itself, Foundation members, and businesses that rely on the project.

We’ll be doing a few things at the event. Make sure to follow @NodeSource on twitter for to-the-minute updates about talks, community events, and more from the conference!

Meet The Team

We’ll have a booth at the event, and we’d be glad to see you there! You can find the NodeSource team at booth G3, between the Microsoft and Heroku booths. We’ll have shirts, hex stickers, and other NodeSource and Node.js swag to grab.

If you’re interested in a 1:1 consultation with the NodeSource team, we’ve set up a page to request a meeting - feel free to fill it out, and we’ll be in touch shortly.

Grokking Asynchronous Work in Node.js

Speaker: Thorsten Lorenz, Senior Engineer at NodeSource

Location: West Meeting Room 122

Time: Thursday October 5, 2017 3:20pm - 3:50pm

Brief: The ability to understand, inspect and debug asynchronous tasks in Node.js remains one of its most glaring deficiencies. A typical production Node.js application will have hundreds of concurrent actions taking place under the hood simultaneously. This soup of activity results in a runtime that is difficult to inspect and debug.

But help is at hand via the new Async Hooks API is being enabled in Node.js to give us deeper insight into the mysteries of Node's asynchronous magic.

Thorsten Lorenz has worked closely with the primary author of Async Hooks, Trevor Norris to ready this new API for public release. In this talk he will explain how these new low-level features can be used to build tools and finally answer the question: what is my Node.js application doing?

The talk will include visual demos that expose the connected activity occurring inside your Node.js process in slow-motion.

Brief: As more and more Node.js are pushed into production there is a critical need to define what it means for a Node.js application to be healthy and performant. We will identify critical metrics "under the hood" involving the Event Loop and GC (garbage collection). Finally we will explore how to quantify and interpret your application metrics to proactively prevent performance issues.