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.
Daniel Bryant talks about the 2016 edition of the seven deadly sins in building microservices, some of the anti-patterns in microservices along with tools for avoiding them.
Emily Reinhold shares stories of how a rapid growth company broke up a monolith into a series of microservices, with practices and lessons that can save time and money.
Ryan Huber talks about some of the ways Slack approaches collecting, inspecting, and communicating security information to the security team and to the individuals in their organization.
Zane Lackey discusses adapting security to change, building security programs, lessons learned from bug bounty programs, running attack simulations and knowing when security has been breached.