-
Always Be Publishing: Continuous Integration & Collaboration in Code Repositories for REST API Docs
API documentation is an often overlooked part of making any API a success. This article explores how to make the documentation part of a continuous integration pipeline keeping it closer to the code itself.
-
Untangling an API-First Transformation at Scale. Lessons Learnt at PayPal – Part 3
This is the third in a three-part series that explores how PayPal has adopted a more API-first approach to building platform services. In this article, we’ll take a closer look at the program aspects and some of the execution and operational challenges that had to be overcome.
-
Untangling an API-first Transformation at Scale. Lessons Learnt at PayPal – Part 2
This is the second in a three-part series that explores how PayPal has adopted a more API-first approach to building platform services. In this article, we’ll take a closer look at how the portfolio of API’s themselves are managed.
Untangling an API-First Transformation at Scale. Lessons Learnt at PayPal – Part 1
In the first of three articles, Erik Hogan describes how PayPal went from a monolithic, siloed architecture to a much more loosely coupled set of over 150 services with well designed, modern APIs. 3
How Zalando Delivers APIs with Radical Agility
InfoQ interviewed Thomas Fraustein, architect at Zalando, about his team’s radical agility development organization that is optimized for an API-first approach. 3
Virtual Panel: Document and Description Formats for Web APIs
In this virtual panel we hear from four individuals deeply involved in the Web API space. Each of them has a unique take on the values, benefits, and costs of documentation and description formats.
An Open API Initiative Update
Tony Tam, creator of the popular Swagger Specification is providing an update on the The Open API Initiative group activity. 1
Creating RESTful Services with T4 Based on Model and Interfaces
Amel Musić demonstrates how T4 can be used to create a flexible code generator that reduces the amount of time and effort it takes to create RESTful services.
HTTP-RPC: A Lightweight Cross-Platform REST Framework
HTTP-RPC is an open-source framework for creating and accessing cross-platform polyglot RESTful web services using a convenient, RPC-like metaphor, while preserving fundamental REST principles. 3
One API, Many Facades?
Beyond any ideal design of your API, reality strikes back with the concrete and differing concerns of varied API consumers. 3
Graph API in a Large Scale Environment
MyHeritage and its FamilyGraph API support millions of API calls every day providing a huge challenge in terms of performance, scalability and security.
Metadata-Driven Design: Building Web APIs for Dynamic Mobile Apps
In this article, Aaron Kendall uses the "metadata-driven design and development" approach by Kevin Perera to show how to rapidly create a mobile application that can evolve during runtime.
