RAML, or the RESTful API Modeling Language, is a relatively new spec based on the YAML format- making it easily read by both humans and machines. But beyond creating a more easily understood spec, Uri Sarid, the creator of RAML, wanted to push beyond our current understandings and create a way to model our APIs before even writing one line of code.
This series focuses on three key areas of "meta-language" for Web APIs: API Description, API Discovery, and API Profiles. You’ll see articles covering all three of these important trends as well as interviews with some of the key personalities in this fast-moving space.
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. 1
Bulk data is usually accessed via files & FTP. As collaboration migrates to APIs, what are the requirements for data APIs? Here we describe a meta-data driven architecture for bulk data ingestion.
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. 6
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. 1
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