Siva Jagadeesan on how to build good web APIs using Resource Oriented Architecture (ROA) and Clojure, showing how to build one with Clojure.
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.
Claudia Perlich keynotes on M6D’s approach to Big Data, using data granularity to build predictive models used for user targeting, bid optimization and fraud detection.
Peter Orlowsky provides insights into the strategy choices that created Getty Images’ API program and the customer/business value the API creates.
Paul Downey explains what they did to redirect all traffic from DirectGov and Business Link to gov.uk, along with the tools, techniques and testing involved for the operation to succeed.
Stephane Dubois shares insight in Xignite’s road building a business model providing APIs for accessing financial data.
John Esser and Russell Barnett discuss Ancestry.com’s SOA implementation capable of supporting continuous delivery, architectural standards used, and how continuous delivery works for them.
Rickard Oberg explains how to expose use-cases to solve the linking problem in RESTful APIs, and how this will simplify both API development, documentation, as well as client development.
Mike Amundsen describes the ALPS standard, a way to define the data and workflow details for a Web application and apply these details consistently regardless of the media type in use. Working examples in the talk also show how this standardized definition can make designing, implementing, documenting, and maintaining Web APIs easier and more consistent across multiple media types.