Jeff Johnson introduces Apollo, a hierarchical NoSQL data system meant to deal with Facebook's distributed storage needs.
Brian Degenhardt discusses lessons that Twitter learned managing a high rate of change and complexity, and how those can be applied anywhere.
Simon Marlow describes a concurrency-based system built with Haskell that allows front-end programmers to write business logic to access all the back-end services in a concise and consistent way.
Keith Adams examines the strengths that made PHP a dominant language in its niche, highlighting Facebook's attempts at remedying its inconsistencies and misfeatures while maintaining its strengths.
Raffi Krikorian discusses the software engineering challenges met re-architecting Twitter and the cultural change impact that came with it.
Christian Legnitto offers insight in some of the tools and processes used by Facebook for pushing new updates to their mobile apps.
Pedro Canahuati describes how Facebook's operations maintains their infrastructure, including challenges faced and lessons learned: prioritizing calls, managing technical debt, incident management.
Keith Adams shares HHVM insights showing how a system can become very performant if it is well tuned.
Keith Adams outlines PHP's strengths and Facebook's attempts at remedying the inconsistencies and misfeatures in the core language.
Juan Manuel and Jesús López González share their experience gathered over five years designing and implementing Speech, a DSL for programming social processes.
Jeremy Cloud discusses SOA at Twitter, approaches taken for maintaining high levels of concurrency, and briefly touches on some functional design patterns used to manage code complexity.
Nicolas Spiegelberg discusses Facebook Messages built on top of HBase, the systems involved and the scaling challenges for handling 500TB of new data per month.