Deepak Nadig, Praveen Alavilli present how PayPal redesigned its APIs based on lessons learnt developing their services in over 14 years, and the principles, patterns and anti-patterns used in API design.
Igor Terzic presents several cases where Ember Data is used in production, and outlines some of the features that are intended to be included in the future.
Anthony Eden explains why they chose to use Erlang for an authoritative DNS, how Erlang helped along the way and some of the challenges faced.
Pedro Canahuati describes how Facebook's operations maintains their infrastructure, including challenges faced and lessons learned: prioritizing calls, managing technical debt, incident management.
Ronny Kohavi shares lessons learned, cultural and scaling challenges conducting hundreds of concurrent online controlled experiments at Bing.
Ben Christensen describes how the Netflix API evolved from a typical one-size-fits-all RESTful API designed to support public developers into a web service platform optimized to handle the diversity and variability of each device and user experience. The talk will also address the challenges involving operations, deployment, performance, fault-tolerance, and rate of innovation at massive scale.
Mike Krieger discusses Instagram's best and worst infrastructure decisions, building and deploying scalable and extensible services.
Keith Adams shares HHVM insights showing how a system can become very performant if it is well tuned.
Thomas Herrmann discusses the advantages, challenges and lessons learned in building a multimedia-heavy, interactive HTML5 application with Ember.js.
Zach Holman discusses the various stumbling blocks GitHub encountered as the company grew over the years.
Ed Cortis shares lessons learned adopting ABW, covering the pilot program, noise/quiet spaces, tools, curtains, card walls, people, logistics, etc.
Alan Griffiths shares the organizational process, the technological challenges and the solutions adopted by a team developing a C++ systems component.