Ben Christensen describes how Neflix has optimized their API using a functional reactive programming (modeled after Rx) in a polyglot Java stack.
Daniel Jacobson shares advice on dealing with evolving APIs based on his experience with Netflix APIs.
Jeff Meisel shares insight in National Instruments’ attempt to create an open API for their software spanning 25 years.
OpenStack Extensions: Challenges and Lessons Learned in the Development and Governance of Extensible REST Services
Jorge Williams shares some of the challenges and lessons learned while adding extensions to OpenStack.
Ian Robinson discusses creating test-driven, resource-oriented and hypermedia-based web APIs, and constructing clients for consuming them.
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.