Jakub Nesetril presents a practical example of prototyping, developing and testing an application using a structured description of its API.
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.
John Musser explains how to transform a good API into a great one based on his experience with thousands of APIs at ProgrammableWeb and API Science.
Francois Lascelles examines the role of API management infrastructure in API Security, API Access Control and API Federation and its interaction with enterprise infrastructure, social identity and application developers.
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.
Kyle Boon reviews 3 frameworks for building RESTful WS- Grails, Dropwizard and Ratpack-, comparing their code readability, maintainability, deployment, metrics collection, scalability and testability.
Blake Dournaee covers the often forgotten back-end architecture for mobile apps which should expose cross-platform APIs to mitigate some of the effects of mobile O/S fragmentation.
Zan Thrash introduces Spock, a Grails testing framework that includes mocking, parameterized tests and an extension API.
Bobby Warner discusses the pros and cons of the available options that Grails developers have for creating RESTful APIs.
Raymond Chen tells the story of Windows’ API evolution from the beginning up to its latest version, WinRT.
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.