Theo Schlossnagle talks about lessons learned in building an always-on distributed time-series database with aggressive quality of service guarantees, and techniques for dealing with bad machines.
David Simons introduces microservices as a developer's API tool, discussing why and when makes sense to use them, and the tools that make it easy to deal with a microservices architecture.
Leonard Garvey and Louis Simoneau discuss how to decompose a monolith, architectural and integration patterns to avoid creating a monolith, and useful patterns and tools along the way.
Evan Broder talks about how Stripe has designed the systems to speed up the development process and how the software infrastructure in their API enables the next tech companies to build faster.
David Greenberg discusses how Two Sigma was able to scale up their research to harness tens of thousands of CPUs and the challenges faced.
Matt Ranney talks about Uber’s growth and how they’ve embraced microservices. This has led to an explosion of new services, crossing over 1,000 production services in early March 2016.
Jessica Kerr introduces Elm, focusing on its architecture: how it overturns what is essential in object-oriented and even back-end functional programming.
Phil Calçado talks about the patterns and techniques DigitalOcean has used over the years to migrate from a monolithic architecture to SOA and microservices.
Brian Goetz looks at some of the challenges and lessons of steering Java through major evolutionary changes, and a sneak peek at where the Java platform is headed.
Saul Caganoff discusses the different use cases for API consumption and the technical affordances API designers can provide to support those use cases.
Peter Bourgon and Matthias Radestock explain the theory behind Weave Mesh, some of the important key features, and demonstrate some exciting use cases, like distributed caching and state replication.
Matthew Erbs discusses the need for applying lessons learned building APIs for customers to the creation of internal APIs for the DevOps team.