This talk will begin by briefly examining what it means for infrastructure to be represented as code. We’ll examine some fundamental software components required for automating infrastructure using code such as GPG, package managers, SSL, and more. We’ll examine some interesting failure cases for these tools and how these shortcomings might make it impossible to truly represent infrastructure as code, for now.
Kafka Streams represents a new design point in the stream processing space. Where most frameworks provide a service for running stream processing applications, Kafka Streams emphasizes low-overhead development that feels more like developing any other application.
We recently replaced a proprietary API management solution with an in-house implementation built with nginx and Lua that is more robust, higher performance, and has greater visibility. Learn about our development process and the overall architecture that allowed us to write high-level code while enjoying native code performance, and how we leveraged other open source tools like Vagrant, Ansible, and OpenStack to build an automation-rich delivery pipeline. We will also take an in-depth look at our capacity management approach that differs from the rate limiting concept prevalent in the API community.
Recently, the Appium project, a large open-source application, decided to rewrite its codebase using ES2015, the newest version of JS. In this talk, I’ll tell the story of what worked and what didn’t. What were the goals of our rewrite and how did our choices deliver on those goals? Specifically, how did ES2015 and the “many modules” approach work for us?
In order to understand something, whether it be user behavior or software infrastructure, we must understand how it moves and changes with time. Unfortunately most of the tools of our trade offer little help in this regard.
What helps us understand the nature of network traffic? Which services are talking to one another and how does this change during failure conditions or a deploy? What helps us understand how user behavior changes over time? And which features provoked these changes? This talk will help prepare you to tackle these problems at a range of scales.
From the abstract: Infrastructure-as-a-service can reduce your scale problems to triviality, lower the capital expenditure of your product launch, and other great buzz phrases. But can it help you rock the mic on karaoke night? Rob Spectre from Twilio finds out by live coding a karaoke machine from an empty project.
Podcast: Play in new window | Download (Duration: 1:08:54 — 263.9MB) | Embed
From the abstract: In this talk, we take a look at some specific Functional Programming patterns that regularly arise in everyday programming. These patterns are used to solve the same problems that DI attempts to by decoupling data types from their dependencies. We explore the algebraic properties of these techniques and discover how they give … Read More
