Having a basic understanding of web based applications is a good foundation for designing a working Web API. But, if you want to create a good API you need a lot more than that. Designing a good API is hard work and it’s easy to feel overwhelmed when it’s your job to make one.
While the process of implementing Web APIs has become common, the tooling for describing, discovering, and understanding the meaning of the tens of thousands of API-based services has yet to settle into a widely-accepted set of standards. There is still quite a bit of opportunity when it comes to defining and implementing tools around the "meta-level" of APIs.
Bulk data is commonly accessed via files & FTP. As the world moves toward APIs to facilitate collaboration, what are the requirements for data APIs? This article describes a meta-data driven architecture for bulk data ingestion. Two APIs operate in parallel to provide data changes as well as the data records themselves. An example demonstrates how API responses are parameterized using meta-data.
In this article, authors provide an overview of current SOA technologies and incremental transition to SOA in legacy environments. They also discuss web services & enterprise application integration. 4
Rounding out our first Web APIs series Mike shares books he recommends for those who want to learn more about designing, implementing, and maintaining APIs for the Web.
Roy Fielding talks to Mike Amundsen about versioning on the Web, why hypermedia is a requirement in his REST style, and the process of designing network software that can adapt over time. 14
In this article, we'll talk about four different real-world implementations of hypermedia starting with how you may already be using hypermedia through image links.
This article provides a brief overview of the design methodology covered in the book "RESTful Web APIs" by Richardson and Amundsen. 3
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