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.
Marton Anka shares lessons learned and technical details scaling LogMeIn over a decade.
Jesper Richter-Reichhelm shares lessons learned from failures while scaling Wooga games to millions of daily users.
Volker Pacher explains why Shutl chose Neo4j when faced with the need of building a new API meant to support business growth, the challenges met during implementation and solutions applied.
Jon Tirsen and Douwe Osinga tell Triposo’s story from a small hobby project to the large architecture of today. Triposo is a mobile phone travel guide.
Trevor Lalish-Menagh shares his experience introducing Kanban, what has worked and what hasn’t.