Mat Ryer takes a look at the code used for a real API running on Google AppEngine, discussing best practices for delivering modern web services.
Rob Valk introduces the JSON-API 1.0 spec, taking a look at JVM ecosystem support for the standard with the katharsis.io library and its integration with the Mule runtime.
David Simons introduces microservices as a developer's API tool, discussing why and when makes sense to use them, and the tools that make it easy to deal with a microservices architecture.
Matthew Erbs discusses the need for applying lessons learned building APIs for customers to the creation of internal APIs for the DevOps team.
Ross Garrett explores how design decisions may be leading to poor UX, discussing the principles of reactive applications and how streaming APIs can deliver significant benefits over RESTful APIs.
Lindsay Holmwood discusses the problems with the traditional approach to digital service delivery in government, and how APIs enable the DTO to help government deliver simpler, faster public services.
Katharina Probst talks about the situations in which server-side scripting is a good solution for applications. She describes Netflix’s first approach, which uses Groovy scripts.
Bruce Haefele shares from the successes and failures implementing an API strategy at Healthdirect Australia.
Neville Li and Igor Maravić cover the evolution of Spotify’s event delivery system, discussing lessons learned moving it into the cloud using Scio, a high level Scala API for the Dataflow SDK.
Tom Adams outlines the problems faced when building small services, and how using a good type system can help, introducing Finch and highlighting how it addresses these concerns.
Adeel Ali presents insights from his database of 11,500 real world APIs.
Andrew Noonan walks through the evolution of the Uber Developer Platform, the launch of Trip Experiences, and the future of the Uber platform.