BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Web API Content on InfoQ

  • APIs with Swagger : An Interview with Reverb’s Tony Tam

    After a flurry of activity from thier open working group, Swagger 2.0 was officially released in September 2014. Our interview took place in March 2015, less than one year from the start of the 2.0 process and right after Reverb announced that the responsibliity for leading the future of the Swagger specification would be handed over to SmartBear, the Massachusetts-based software tools company.

  • The Power of RAML

    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.

  • Article Series: Description, Discovery, and Profiles : The Next Level in Web APIs

    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.

  • From Doodles to Delivery: An API Design Process

    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.

  • Description, Discovery, and Profiles: A Primer

    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.

  • Service-Oriented Architecture and Legacy Systems

    In this article, authors provide an overview of current SOA technologies and how to evolve in legacy environments. They also discuss the topics of SOAP vs. REST web services, Enterprise Application Integration and incremental transition to SOA in legacy environments.

  • REST-y Reader

    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 on Versioning, Hypermedia, and REST

    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.

  • Implementing Hypermedia

    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.

  • A Web API Design Methodology

    This article provides a brief overview of the design methodology covered in the book "RESTful Web APIs" by Richardson and Amundsen.

  • Making the Case for an API Roadmap

    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.

  • An Interview with HAL Creator Mike Kelly

    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.

BT