JSFoo: round the year submissions

A large percentage of Node application misbehavior can be effectively diagnosed and root cause identified through the in-built tracing capabilities of Node/V8. There are a number of under-documented, yet very powerful tracing options which we can leverage in development, testing and production phases to validate that the application architecture and design is indeed reflected in the code or not, without ever instrumenting it.In this presentation, I will talk about the “top 10” tracing options for Node/V8, ranging from the most simple Javascript method tracing to turning off specific JIT compiler options to diagnose and resolve complex crashes or functional issues.

Outline

• While learning a language and its APIs can be easy for a programmer, Problem determination requires deeper insights into the inner working of the execution environment, not just the language semantics

• Any production scale application would require problem determination applied to as an essential ingredient, in at least one milestone of its development lifecycle.

• The presentation aims to educate the audience with the powerful tracing option that is intrinsic to Node.js, and that caters to a number of real world production issues.

• Focus on issues that are experienced in the field - insight gathered from the support experience. So directly consumable.

Requirements

None

Speaker bio

Gireesh Punathil is an Architect and Software developer with IBM India Software Labs, predominantly working in Java and Node.js. In 15 years of his career, he has been porting, developing and debugging web servers, virtual machines and compilers. His expertise is in problem isolation and determination of large and complex software modules. He has spoken at several Node.js and Java conferences.