Stefanie Schirmer talks about the case study of building an API-first architecture at Etsy, why they built it, the tools used, the mistakes made and the lessons learnt along the way.
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.
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.
Steven Willmott looks at how APIs’ value helps genuine success for an API program and an organization's platform initiatives as a whole, including examples and takeaways.
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.