Standard

An Exploratory Study on Faults in Web API Integration in a Large-Scale Payment Company. / Aué, Joop; Aniche, Maurício; Lobbezoo, Maikel; van Deursen, Arie.

ICSE-SEIP '18: 40th International Conference on Software Engineering: Software Engineering in Practice Track. Association for Computing Machinery (ACM), 2018. p. 13-22.

Research output: Scientific - peer-reviewConference contribution

Harvard

Aué, J, Aniche, M, Lobbezoo, M & van Deursen, A 2018, An Exploratory Study on Faults in Web API Integration in a Large-Scale Payment Company. in ICSE-SEIP '18: 40th International Conference on Software Engineering: Software Engineering in Practice Track. Association for Computing Machinery (ACM), pp. 13-22, ICSE 2018, Gothenburg, Sweden, 27/05/18. DOI: 10.1145/3183519.3183537

APA

Aué, J., Aniche, M., Lobbezoo, M., & van Deursen, A. (2018). An Exploratory Study on Faults in Web API Integration in a Large-Scale Payment Company. In ICSE-SEIP '18: 40th International Conference on Software Engineering: Software Engineering in Practice Track (pp. 13-22). Association for Computing Machinery (ACM). DOI: 10.1145/3183519.3183537

Vancouver

Aué J, Aniche M, Lobbezoo M, van Deursen A. An Exploratory Study on Faults in Web API Integration in a Large-Scale Payment Company. In ICSE-SEIP '18: 40th International Conference on Software Engineering: Software Engineering in Practice Track. Association for Computing Machinery (ACM). 2018. p. 13-22. Available from, DOI: 10.1145/3183519.3183537

Author

Aué, Joop ; Aniche, Maurício ; Lobbezoo, Maikel ; van Deursen, Arie. / An Exploratory Study on Faults in Web API Integration in a Large-Scale Payment Company. ICSE-SEIP '18: 40th International Conference on Software Engineering: Software Engineering in Practice Track. Association for Computing Machinery (ACM), 2018. pp. 13-22

BibTeX

@inbook{d8b594fef6d8412a83b7cba8870f6cc9,
title = "An Exploratory Study on Faults in Web API Integration in a Large-Scale Payment Company",
abstract = "Service-oriented architectures are more popular than ever, and increasingly companies and organizations depend on services offered through Web APIs. The capabilities and complexity of Web APIs differ from service to service, and therefore the impact of API errors varies. API problem cases related to Adyen's payment service were found to have direct considerable impact on API consumer applications. With more than 60,000 daily API errors, the potential impact is enormous. In an effort to reduce the impact of API related problems, we analyze 2.43 million API error responses to identify the underlying faults. We quantify the occurrence of faults in terms of the frequency and impacted API consumers. We also challenge our quantitative results by means of a survey with 40 API consumers. Our results show that 1) faults in API integration can be grouped into 11 general causes: invalid user input, missing user input, expired request data, invalid request data, missing request data, insufficient permissions, double processing, configuration, missing server data, internal and third party, 2) most faults can be attributed to the invalid or missing request data, and most API consumers seem to be impacted by faults caused by invalid request data and third party integration; and 3) insufficient guidance on certain aspects of the integration and on how to recover from errors is an important challenge to developers.",
keywords = "web engineering, web API integration, webservices",
author = "Joop Aué and Maurício Aniche and Maikel Lobbezoo and {van Deursen}, Arie",
year = "2018",
doi = "10.1145/3183519.3183537",
pages = "13--22",
booktitle = "ICSE-SEIP '18: 40th International Conference on Software Engineering: Software Engineering in Practice Track",
publisher = "Association for Computing Machinery (ACM)",
address = "United States",

}

RIS

TY - CHAP

T1 - An Exploratory Study on Faults in Web API Integration in a Large-Scale Payment Company

AU - Aué,Joop

AU - Aniche,Maurício

AU - Lobbezoo,Maikel

AU - van Deursen,Arie

PY - 2018

Y1 - 2018

N2 - Service-oriented architectures are more popular than ever, and increasingly companies and organizations depend on services offered through Web APIs. The capabilities and complexity of Web APIs differ from service to service, and therefore the impact of API errors varies. API problem cases related to Adyen's payment service were found to have direct considerable impact on API consumer applications. With more than 60,000 daily API errors, the potential impact is enormous. In an effort to reduce the impact of API related problems, we analyze 2.43 million API error responses to identify the underlying faults. We quantify the occurrence of faults in terms of the frequency and impacted API consumers. We also challenge our quantitative results by means of a survey with 40 API consumers. Our results show that 1) faults in API integration can be grouped into 11 general causes: invalid user input, missing user input, expired request data, invalid request data, missing request data, insufficient permissions, double processing, configuration, missing server data, internal and third party, 2) most faults can be attributed to the invalid or missing request data, and most API consumers seem to be impacted by faults caused by invalid request data and third party integration; and 3) insufficient guidance on certain aspects of the integration and on how to recover from errors is an important challenge to developers.

AB - Service-oriented architectures are more popular than ever, and increasingly companies and organizations depend on services offered through Web APIs. The capabilities and complexity of Web APIs differ from service to service, and therefore the impact of API errors varies. API problem cases related to Adyen's payment service were found to have direct considerable impact on API consumer applications. With more than 60,000 daily API errors, the potential impact is enormous. In an effort to reduce the impact of API related problems, we analyze 2.43 million API error responses to identify the underlying faults. We quantify the occurrence of faults in terms of the frequency and impacted API consumers. We also challenge our quantitative results by means of a survey with 40 API consumers. Our results show that 1) faults in API integration can be grouped into 11 general causes: invalid user input, missing user input, expired request data, invalid request data, missing request data, insufficient permissions, double processing, configuration, missing server data, internal and third party, 2) most faults can be attributed to the invalid or missing request data, and most API consumers seem to be impacted by faults caused by invalid request data and third party integration; and 3) insufficient guidance on certain aspects of the integration and on how to recover from errors is an important challenge to developers.

KW - web engineering

KW - web API integration

KW - webservices

U2 - 10.1145/3183519.3183537

DO - 10.1145/3183519.3183537

M3 - Conference contribution

SP - 13

EP - 22

BT - ICSE-SEIP '18: 40th International Conference on Software Engineering: Software Engineering in Practice Track

PB - Association for Computing Machinery (ACM)

ER -

ID: 38321936