Are you tantalized by Systems We Love but you don't know what proposal to submit? For those looking for proposal guidance, my advice is simple: find the love. Just as every presentation title at !!Con must assert its enthusiasm by ending with two bangs, you can think of every talk at Systems We Love as beginning with an implicit "Why I love..." So instead of a lecture on, say, the innards of ZFS (and well you may love ZFS!), pick an angle on ZFS that you particularly love. Why do you love it or what do you love about it? Keep it personal: this isn't about asserting the dominance of one system—this is about you and a system (or an aspect of a system) that you love.
It took a little while to get the logistics down, but I'm very happy to report that Systems We Love is on: December 13th in San Francisco! To determine the program, I am honored to be joined by an extraordinary program committee: hailing from a wide-range of backgrounds, experience levels, and interests—and united by a shared love of systems. So: the call for proposals is open—and if you have a love of systems, we hope that you will consider submitting a proposal and/or joining us on December 13th!
An overview of post-mortem debugging pitfalls when using promises.
Building a simple Hello World application with ContainerPilot and the AutoPilot Pattern using Node.js.
A tutorial on debugging Node.js core dumps with MDB.
For this entry, we're going to be focusing on how the Operating System sees NICs, what abstractions they provide together, how things have changed to deal with the increased tenancy and performance demands, and then finally where we're going next with all this. We're going to focus on where scalability problems have come about and talk about how they've been solved.
An overview of how to build observable Node.js applications. The solutions presented are useful for designing and building reliable and more debuggable applications, especially those applications that are microservice oriented.
Answers to your questions about the powerful networking features in Triton.
Introducing two new modules to make implementing Autopilot Pattern applications in Node.js even easier.
Watch the screencast and learn how to install the Triton CLI tool and use CloudAPI to manage containers, VMs, networks, and storage in Triton data centers.
It's been said that we don't really understand a system until we understand how it fails. Despite having written a (toy) TCP implementation in college and then working for several years in industry, I'm continuing to learn more deeply how TCP works — and how it fails. What's been most surprising is how basic some of these failures are. They're not at all obscure. I'm presenting them here as puzzlers, in the fashion of Car Talk and the old Java puzzlers. Like the best of those puzzlers, these are questions that are very simple to articulate, but the solutions are often surprising. And rather than focusing on arcane details, they hopefully elucidate some deep principles about how TCP works.
Watch the screencast of how to install Docker, dockerize an app, and run it in production on Triton Cloud
Join me, a front-end dev and new Docs Editor for Joyent, while I dockerize my first app and then run it in production on Triton Cloud.
Applications developed with the Autopilot Pattern have containers acting as autonomous actors using an external service catalog like Consul or etcd for coordination. Both services bring assumptions that bring challenges to serverless environments.
Something that got a little lost in the excitement of Samsung’s recent acquisition of Joyent was dtrace.conf(16), our quadrennial (!) unconference on DTrace. The videos are up, and in the spirit of Adam Leventhal‘s excellent wrap-ups from dtrace.conf(08) and dtrace.conf(12), I wanted to provide a survey of the one-day conference and its content.