Michael Brunton-Spall shares his experience re-architect The Guardian’ Content API from a system based on Solr to a message queue cloud service based upon Elastic Search, without any downtime.
Ben Christensen explains how Netflix optimizes server’s interaction with more than 800 client devices by creating customized concurrent service endpoints with RxJava and Hystrix.
An important use case for mobile apps is providing instant access to remote resources, whether it be social networks or enterprise services. How can the server API and the client app be designed in parallel to improve the experience? This panel discusses things to do and to avoid in building APIs for mobile apps, and answer attendees' questions on the topic.
Siva Jagadeesan on how to build good web APIs using Resource Oriented Architecture (ROA) and Clojure, showing how to build one with Clojure.
Sumit Sharma, Bruno Pedro, Heather O’Sullivan discuss the status of enterprise APIs, providing insight in adopting API at the enterprise level, plus offering insight in creating such APIs.
Jakub Nesetril, Tony Tam, Kirsten Jones share tools and tips for building great APIs.
Peter Orlowsky provides insights into the strategy choices that created Getty Images’ API program and the customer/business value the API creates.
Giovanni Asproni expands upon the idea that usable APIs help writing clean code.
Irakli Nadareishvili, Jon Moore, and Anthony Cuellar share insight in creating teams and building media APIs for distributing content.
Andrew Mager, Paul Osman, Evan Stein and R. Kevin Nelson share from their experience introducing a music API culture into their companies and developing such APIs.
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.