Node+JS Interactive

Ever had trouble fixing issues in your Node.js production application? Sometimes those issues can't be reproduced in development or staging environments, and in this cases having a debugger which can be used in production is extremely helpful. llnode is a lldb plugin which enables inspection of Node.js processes and core dumps. In this workshop, you'll learn how to use llnode to find and fix issues faster and reliably, without bloating your application with logs or compromising its performance.

We know the delicate stack decision-making dance to adhere to ‘use the right tools for the job’ (of course, w/ Node.js in the mix). Critical cloud provider decisions try to thread the performance, convenience, and pricing needle. Top availability here, great tools there, and discounts everywhere, makes those choices tough. Tight coupling early on makes ultimately the finding the right provider even more difficult.

However a Kubernetes cluster, usually only a few clicks away, makes it possible to build, test, lift, and shift providers. In this talk, we’ll discuss the importance of being mobile to take advantage of the features and pricing that fit your needs. We’ll dive deep into lifting and shifting your Node.js project from one provider to another with Kubernetes. Finally, we’ll design a lift and shift-ready Node.js app to test performance and analyze pricing on AWS, GCloud and Azure.

JSON has become the defacto standard for transporting data and metadata - anything from function arguments to large multimedia blobs and from query results to API data exchange media. In Cloud deployments, we foresee an exponential increase of JSON payload across distributed end-points, causing performance bottleneck in the application. In this talk, I present truly asynchronous version of standard JSON APIs that is highly scalable, fault-tolerant and highly consumable. The key functions of these APIs are to perform marshaling / un-marshaling of massive data incrementally and yielding back to the application occasionally, improving the overall concurrency of the system, improving concurrency level by 10 times above 1MB of JSON data.