The authors discuss about the lessons learned from all the biggest sites on the internet about how to build scalable and resilient architectures.
Mike Beltzner describes the tools and techniques used to keep Pinterest's platform stable and responsive. Garrett Moon dives into the technology they developed.
Jafar Husain shows the Reactive Extensions (Rx) library which allows to treat events as collections, how Netflix uses Rx on the client and the server, allowing to build end-to-end reactive systems.
Logan Linn explores the design and implications of an architecture built around immutable data structures using ClojureScript and Om, a ClojureScript interface to Facebook's React.
Aaron Gardner pulls back the covers on the Etsy Search ecosystem and how they got here -- the good, the bad, and the funky.
Karl Scotland tells the story of a world wide athletic community, wondering what would happen if there were a similar community of small teams focused on work knowledge.
Thomas Epping considers that case studies, even successful ones, should not be blindly applied everywhere, but one should take only what’s useful for one’s circumstance.
Sid Anand discusses the architectural and development practices adopted by LinkedIn as a continuous growing company.
This talk goes over the design motivation for Zen and describe its internals including the API, type system and HBase backend.
John Bunting talks about different services Tumblr has built and how their architecture helps them be fault tolerant as they continue to grow.
Andy Vaughn gives attendees a case study of how changing the development model and release cycle of a 5 year old software product to continuous delivery greatly improved the product.
Geoff McDonald describes how the company succeeds in engaging workers by providing an inspirational business purpose, a decision making framework and focusing on employee well-being.