Web API growing pains

Loosely coupled yet strongly tied

Journal article (2015)

Authors

T.A. Rodrigues Espinha Software Engineering - EEMCS
A.E. Zaidman Software Engineering - EEMCS
H.G. Gross Esslingen University
Research Group
Software Engineering (EEMCS) (TU Delft)
Copyright: © 2015 T.A. Rodrigues Espinha, A.E. Zaidman, H.G. Gross
DOI: https://doi.org/10.1016/j.jss.2014.10.014
Software evolution Web API Breaking changes
More Info
expand_more

Published Date

01-01-2015

Language

English

Reuse Rights

Other than for strictly personal use, it is not permitted to download, forward or distribute the text or part of it, without the consent of the author(s) and/or copyright holder(s), unless the work is under an open content license such as Creative Commons.

Faculty

Electrical Engineering, Mathematics and Computer Science

Department

Software Technology

Research Group

Software Engineering

Abstract

Web APIs provide a systematic and extensible approach for application-to-application interaction. Developers using web APIs are forced to accompany the API providers in their software evolution tasks. In order to understand the distress caused by this imposition on web API client developers we perform a semi-structured interview with six such developers. We also investigate how major web API providers organize their API evolution, and we explore how this affects source code changes of their clients. Our exploratory qualitative study of the Twitter, Google Maps, Facebook and Netflix web APIs analyzes the state of web API evolution practices and provides insight into the impact of service evolution on client software. In order to complement the picture and also understand how web API providers deal with evolution, we investigate the server-side and client-side evolution of two open-source web APIs, namely VirtualBox and XBMC. Our study is complemented with a set of observations regarding best practices for web API evolution.

Files

EspinhaJSS_2.pdf
(.pdf | 0.872 Mb)