Steven Ihde and Karan Parikh discuss about tools and frameworks built in order to help LinkedIn's transition to microservices, including their URN resolution engine and the Rest.li API Hub.
Rob Cromwell talks about the evolution of Inkling's culture, and the many lessons learned in building "conscious" teams that work well together in the pursuit of technical excellence.
Paul Osman discusses their experiences evolving 500px from a single, monolithic Ruby on Rails application to a series of composable microservices written in Ruby and Go.
Martin Thompson focuses on the design of Aeron, what they learned trying to achieve consistent performance, and challenges performing UDP messaging in a lock-free and wait-free manner.
Caitie McCaffrey does an overview of Orleans, the challenges faced when building the Halo 4 services, and why the Actor Model and Orleans in particular were utilized to solve these problems.
Alex Blewitt introduces the history behind Swift, why it was created, how it differs from Objective-C and how Swift is compiled and executed under the covers.
Russ Olsen tells the moon landing story and how it has affected the software development.
Gian Merlino presents the advantages, challenges, and best practices to deploying and maintaining lambda architectures in the real world, using the infrastructure at Metamarkets as a case study.
The panelists discuss Java performance topics, bringing their specific experiences to bear.
Julien Le Dem discusses the advantages of a columnar data layout, specifically the features and design choices Apache Parquet uses to achieve goals of interoperability, space and query efficiency.
Mike Barker shares lessons learned at LMAX Exchange: starting from a clean domain model is imperative and understanding the trade-offs between performance and safety/generality/functionality.
Dustin Getz,Daniel Miladinov demonstrate using Facebook React to build a CRUD editor, highlighting React's application of functional programming and immutability to manage complex application state.