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.
Michael Wise discusses the journey from having data integrated across an organization, to employing data science to make good use of it.
Phil Calçado talks about the patterns and techniques DigitalOcean has used over the years to migrate from a monolithic architecture to SOA and microservices.
Saul Caganoff discusses the different use cases for API consumption and the technical affordances API designers can provide to support those use cases.
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.
Bruce Haefele shares from the successes and failures implementing an API strategy at Healthdirect Australia.
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.
Uli Holtel discusses the principles of hypermedia APIs, how to decouple from media type formats, using profiles, 'fully dynamic' vs. 'tightly coupled' client, tools, code artifacts and examples.
Todd Brackley discusses accessing the “network of data” through a RESTful hypermedia API, exposing it to developers, testers, analysts and clients.
Rob Zazueta introduces RESTed NARWHL, a design framework for building RESTful APIs that adhere to current best practices while being able to rapidly adapt to change.