software development process

Understanding Performance with DTrace (While The Customer Yells at You): A Case Study

Location: Salon C
April 12th, 2016
11:30 AM - 12:30 PM

You’ve built some software that users love, and while its use starts to become more frequent it also becomes more critical. Suddenly the failures, inevitable and previously merely a nuisance, have become critical and emotionally fraught as your users see reputation, revenue, and even job security imperiled! Bugs come in many flavors. None quicken the pulse as much as a critical system suffering from poor performance. They can be hard to drive to root cause, hard to fix, hard to reproduce, and even hard for the user to describe beyond “it’s slow (fix it!)”. Fortunately we’re not completely alone in

Adam Leventhal

Co-Creator, DTrace

The Node Module Diaries: Large App Architecture from the Trenches

Location: Salon E
April 12th, 2016
1:30 PM - 2:30 PM

The Node.js community has evolved a number of application design patterns for JavaScript applications, including application-internal package management patterns. The all-around awesomeness of NPM has lent itself to a hyper-modular approach for Node code not seen in many other language communities. This is great, especially when writing open-source tools designed to be used by others' applications. Meanwhile, the "microservices" or "distributed systems" architectural patterns have begun their ascendancy. It makes sense to isolate components so they can be managed independently of one another. One could be forgiven for thinking that "many modules" and "microservices" are similar answers to similar questions,

Jonathan Lipps

Director of Engineering, Sauce Labs