Roy Fielding talks to Mike Amundsen about versioning on the Web, why hypermedia is a requirement in his REST style, the process of designing network software that can adapt over time, and the challenge of thinking at the scale of decades.
In this article, we'll talk about four different real-world implementations of hypermedia: how you may already be using hypermedia through image links, how GitHub uses the Link header for pagination, using hypermedia in constrained systems like iOS, and how Balanced uses hypermedia principles to build their product.
Mike Amundsen's series "Designing APIs for the Web" is a straightforward dive into API design suitable for a broad set of stakeholders. This article reviews the series so you know what to expect.
Chris Haddad explains why one should create a roadmap for an API, providing advice on avoiding common API pitfalls, creating business value and monetizing API assets. 1
As part of our ongoing series on Web APIs Mike Amundsen talks to Mike Kelly about his reasons for creating HAL and his experiences over the last three years with web developers and the API community 4
This article, the first of a new series, examines APIs from a business perspective. It covers the importance of tying your APIs back to your business value, with examples from Amazon and Twilio. 2
This series takes the reader on a journey from determining the business case for APIs to a design methodology, meeting implementation challenges and maintaining public APIs on the Web over time.
The article describes the general outline of the Stats Anomalies Detector developed at MyHeritage and provides a detailed explanation of how to enhance the code to meet your company’s needs.
What are the practical concerns associated with running microservice systems? And what you need to know to embrace the power of smaller services without making things too hard? 2
Many Web API designers claim their are RESTful, but their APIs have little in common with REST. What can be done to make a web service API truly RESTful? 8
Ganesh Prasad proposes minimizing service dependencies in a SOA implementation rather than avoiding point-to-point connections in order to obtain a more flexible system that can evolve over time. 1