Ben Hale explains how to design and test a RESTful API with Spring MVC, providing an example of a simple game application showing the design principles used.
Mike Amundsen discusses the theory behind building hypermedia APIs combined with real life cases exemplifying the successes and failures of such an endeavor.
Rob Daigneau discusses some of the challenges met when creating and maintaining web APIs, impediments and design patterns for web API evolution.
Mike Amundsen explores a way of designing hypermedia APIs based on messages instead of URIs, plus documenting, extending, versioning and registering hypermedia designs.
Andrew Phillips discusses Cloud API 2.0: the current state of cloud computing, why a Cloud API, the choices made while designing jClouds API, and how to consume such an API.
Daniel Jacobson covers the history of Netflix’s APIs, adaptation for the cloud, development and testing, resiliency, and the future of their APIs.
Evan Cooke discussing ways of building Simple APIs with fast signup, a clear value proposition, efficient quick start, concise documentation, easy authentication and debuggable.
Gregory Brail discusses about APIs, what an API platform is, how the typical API call flows-security, authorization, authentication, caching, etc., and some of the challenges in using an API platform.
Giovanni Asproni presents techniques for writing usable APIs: using user's perspective, naming, the caller should have the control, explicit context, error reporting, logging, organizing.
At QCon 2008, Neal Gafter discusses how to evolve a widely deployed language without causing disruption using planned changes for JDK7 (superpackages, closures, annotations on types, type inference, exception handling, and self types) as an example. He examines how the changes are conditioned by preexisting language design choices, and discusses their influence on API design.